Docs » Available host and application monitors in Splunk Observability Cloud » Configure application exporters and receivers for monitoring » SignalFx Forwarder

SignalFx Forwarder 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the signalfx-forwarder monitor type to run an HTTP server that listens for data points and trace spans, and forward them to Splunk Observability Cloud. This integration supports the latest formats for data points and spans that the Splunk ingest API endpoint supports.

This integration is available on Linux and Windows.

Benefits 🔗

After you configure the integration, you can access these features:

Installation 🔗

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example 🔗

To activate this integration, add the following to your Collector configuration:

    type: signalfx-forwarder
    ... # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

      receivers: [smartagent/signalfx-forwarder]
      receivers: [smartagent/signalfx-forwarder]

Note that the defaultSpanTagsFromEndpoint and extraSpanTagsFromEndpoint config options are not compatible with the signalfx-forwarder receiver.

Configuration settings 🔗

The following table shows the configuration options for the signalfx-forwarder integration:








The host and port on which to listen for data points. The listening server accepts data points on the same HTTP path as the ingest endpoint or gateway. For example, /v2/datapoint or /v1/trace. Requests to other paths return errors with HTTP code 404. The default value is




HTTP timeout duration for both read and write operations. Accepts a duration string for The default value is 5s.




Whether to emit internal metrics about the HTTP listener. The default value is false.

Metrics 🔗

There are no metrics available for this integration.

Troubleshooting 🔗

If you are not able to see your data in Splunk Observability Cloud, try these tips:

  • Submit a case in the Splunk Support Portal.

    • Available to Splunk Observability Cloud customers

  • Call Splunk Customer Support

    • Available to Splunk Observability Cloud customers

  • Ask a question and get answers through community support at Splunk Answers.

    • Available to Splunk Observability Cloud customers and free trial users

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide

To learn about even more support options, see Splunk Customer Success.