SignalFx receiver 🔗
The SignalFx receiver is a native OpenTelemetry component that allows the Splunk Distribution of the OpenTelemetry Collector to collect data in SignalFx proto format. Supported pipeline types are metrics and logs. See Process your data with pipelines for more information.
Note
While the SignalFx Smart Agent has reached End of Support, OTel native components such as the Smart Agent receiver, the SignalFx receiver, and the SignalFx exporter are available and supported. For information on the exporter, see SignalFx exporter.
The SignalFx receiver accepts:
Metrics in the SignalFx proto format. For more information, see SignalFx metrics protobuf .
Events (logs) in the SignalFx proto format. For more information, see Send Traces, Metrics, and Events in the Splunk Developer Program documentation.
Get started 🔗
Note
This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector in the metrics and logs/signalfx pipelines when deploying in host monitoring (agent) mode. See Collector deployment modes for more information.
For details about the default configuration, see Configure the Collector for Kubernetes with Helm, Collector for Linux default configuration, or Collector for Windows default configuration. You can customize your configuration any time as explained in this document.
Follow these steps to configure and activate the receiver:
Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
Configure the receiver as described in this doc.
Restart the Collector.
Default configuration 🔗
Caution
Don’t remove the signalfx receiver from the default configuration. If you need to change its settings, use the existing receiver or create a separate receiver configuration.
To use the signalfx receiver in the Splunk Distribution of the OpenTelemetry Collector, add the following to your config file:
receivers:
signalfx:
endpoint: 0.0.0.0:9943
# Whether to preserve incoming access token and
# use instead of exporter token. Default value is false.
# access_token_passthrough: true
Next, configure both the metrics and logs pipelines. Make sure to also add the SignalFx exporter as in the following example:
service:
pipelines:
metrics:
receivers: [signalfx]
processors: [memory_limiter, batch]
exporters: [signalfx]
logs:
receivers: [signalfx]
processors: [memory_limiter, batch]
exporters: [signalfx]
Sample configuration 🔗
This is a sample config for the SignalFx receiver:
signalfx:
signalfx/allsettings:
# endpoint specifies the network interface and port which will receive
# SignalFx metrics.
endpoint: localhost:9943
access_token_passthrough: true
signalfx/tls:
tls:
cert_file: /test.crt
key_file: /test.key
Settings 🔗
The following table shows the configuration options for the SignalFx receiver:
Caution
If you use the access_token_passthrough setting with any exporter other than the SignalFx exporter, the receiver might reveal all organization access tokens. If you activate this setting, you must use the SignalFx receiver with the SignalFx exporter.
Troubleshooting 🔗
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal .
Contact Splunk Support .
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.