SignalFx

Author: n | 2025-04-24

signalfx signalfx-review signalfx-features signalfx-download signalfx-tutorial signalfx-setup Updated ; Improve this page Add a

signalfx/signalfx-vsphere: SignalFx Integration for

SignalFx Resource ProviderThe SignalFx resource provider for Pulumi lets you manage SignalFx resources in your cloud programs. To usethis package, please install the Pulumi CLI first.InstallingThis package is available in many languages in the standard packaging formats.Node.js (Java/TypeScript)To use from JavaScript or TypeScript in Node.js, install using either npm:$ npm install @pulumi/signalfxor yarn:$ yarn add @pulumi/signalfxPythonTo use from Python, install using pip:$ pip install pulumi_signalfxGoTo use from Go, use go get to grab the latest version of the library$ go get github.com/pulumi/pulumi-signalfx/sdk/v7.NETTo use from .NET, install using dotnet add package:$ dotnet add package Pulumi.SignalfxConfigurationThe following configuration points are available:signalfx:authToken - (Required) The auth token for authentication. This can also be set via the SFX_AUTH_TOKENenvironment variable.signalfx:apiUrl - (Optional) The API URL to use for communicating with SignalFx. This is helpful for organizationswho need to set their Realm or use a proxy. Note: You likely want to change customAppUrl too!signalfx:customAppUrl - (Optional) The application URL that users should use to interact with assets in the browser.This is used by organizations using specific realms or those with a custom SSO domain.ReferenceFor further information, please visit the SignalFx provider docs or for detailed reference documentation, please visit the API docs.

signalfx/signalfx-vsphere: SignalFx Integration for VMware

The cat command assigns the CONFIG_YAML parameter to the YAML. The docker run command expands and assigns the parameter CONFIG_YAML to the environment variable SPLUNK_CONFIG_YAML. Note that YAML requires whitespace indentation to be maintained.CONFIG_YAML=$(cat receivers: hostmetrics: collection_interval: 1s scrapers: cpu:exporters: debug: # Can be changed to info verbosity: detailedservice: pipelines: metrics: receivers: [hostmetrics] exporters: [logging]END)docker run --rm \ -e SPLUNK_CONFIG_YAML=${CONFIG_YAML} \ --name otelcol quay.io/signalfx/splunk-otel-collector:latest # Use a semantic versioning (semver) tag instead of the ``latest`` tag. # Semantic versioning is a formal convention for determining the version # number of new software releases.Binary file 🔗To install the Collector using the binary file, follow these steps:Download the binary for your architecture from GitHub releases .If you’re not using an existing or custom config file, download the default config file for the Collector. See more at Collector for Linux default configuration.Run the binary from the command line:# see available command-line options$ dir>/otelcol__ --helpUsage of otelcol: --config string Locations to the config file(s), note that only a single location can be set per flag entry e.g. --config=/path/to/first --config=path/to/second. (default "[]") --feature-gates string Comma-delimited list of feature gate identifiers. Prefix with '-' to disable the feature. '+' or no prefix will enable the feature. (default "[]") --no-convert-config Do not translate old configurations to the new format automatically. By default, old configurations are translated to the new format for backward compatibility. --set string Set arbitrary component config property. The component has to be defined in the config file and the flag has a higher precedence.

GitHub - signalfx/signalfx-vsphere: SignalFx Integration for

. signalfx signalfx-review signalfx-features signalfx-download signalfx-tutorial signalfx-setup Updated ; Improve this page Add a

signalfx/signalfx-agent: The SignalFx Smart Agent

The Collector in --read-only mode and using any Smart Agent receiver’s legacy collectd monitor types, you need to provide a writable config directory similar to --read-only --tmpfs /usr/lib/splunk-otel-collector/agent-bundle/run:uid=999,gid=999 (default) or as configured by the Smart Agent extension’s collectd::configDir path.Create a custom Docker configuration 🔗You can provide a custom configuration file instead of the default configuration file. Use the environment variable SPLUNK_CONFIG or the --config command line argument to provide the path to this file.You can also use the environment variable SPLUNK_CONFIG_YAML to specify your custom configuration file at the command line. This is useful in environments where access to the underlying file system is not readily available. For example, in AWS Fargate, you can store your custom configuration YAML in a parameter in the AWS Systems Manager Parameter Store, then in your container definition specify SPLUNK_CONFIG_YAML to get the configuration from the parameter.Command line arguments take precedence over environment variables. This applies to --config and --mem-ballast-size-mib. SPLUNK_CONFIG takes precedence over SPLUNK_CONFIG_YAML. For example:docker run --rm -e SPLUNK_ACCESS_TOKEN=12345 -e SPLUNK_REALM=us0 \ -e SPLUNK_CONFIG=/etc/collector.yaml -p 13133:13133 -p 14250:14250 \ -p 14268:14268 -p 4317:4317 -p 6060:6060 -p 8888:8888 \ -p 9080:9080 -p 9411:9411 -p 9943:9943 \ -v "${PWD}/collector.yaml":/etc/collector.yaml:ro \ # A volume mount might be required to load the custom configuration file. --name otelcol quay.io/signalfx/splunk-otel-collector:latest # Use a semantic versioning (semver) tag instead of the ``latest`` tag. # Semantic versioning is a formal convention for determining the version # number of new software releases.Use the following configuration to collect and log CPU metrics.

signalfx/signalfx-agent: The SignalFx Smart Agent - GitHub

To override the default config file path for the Fluentd service. To do this, copy the systemd environment file from /etc/otel/collector/fluentd/splunk-otel-collector.conf to /etc/systemd/system/td-agent.service.d/splunk-otel-collector.conf.Ensure that the td-agent service user/group has permissions to access to the config file(s) from the previous step.Restart the Fluentd service to apply the changes by running systemctl restart td-agent.View Fluentd service logs and errors in /var/log/td-agent/td-agent.log.See Fluentd configuration for general Fluentd configuration details.Docker 🔗The Linux docker image of the Splunk Distribution of the OpenTelemetry Collector contains a multiarch manifest that specifies the images for AMD64, ARM64, and ppc64le architectures. Docker uses this manifest to download the correct image for the target platform.Run the following command to install the package using Docker:docker run --rm -e SPLUNK_ACCESS_TOKEN=12345 -e SPLUNK_REALM=us0 \ -p 13133:13133 -p 14250:14250 -p 14268:14268 -p 4317:4317 -p 6060:6060 \ -p 7276:7276 -p 8888:8888 -p 9080:9080 -p 9411:9411 -p 9943:9943 \ --name otelcol quay.io/signalfx/splunk-otel-collector:latest # Use a semantic versioning (semver) tag instead of the ``latest`` tag. # Semantic versioning is a formal convention for determining the version # number of new software releases.The following list provides more information on the docker run command options:--rm automatically removes the container when it exits.-e sets simple (non-array) environment variables in the container you’re running, or overwrite variables that are defined in the Dockerfile of the image you’re running.-p publishes a container’s port(s) to the host.Run the following command to run an interactive bash shell on the container and see the status of the Collector:docker exec -it containerID bashNoteIf you are running

signalfx-agent module - github.com/signalfx/signalfx-agent - Go

. signalfx signalfx-review signalfx-features signalfx-download signalfx-tutorial signalfx-setup Updated ; Improve this page Add a signalfx signalfx-review signalfx-features signalfx-download signalfx-tutorial signalfx-setup Updated ; claranet / signalfx-azure-function-python Star 0. Code Issues Pull