Docs » Configure application receivers » Configure application exporters and receivers for monitoring » SignalFx Forwarder

SignalFx Forwarder 🔗

Description 🔗

The Splunk Distribution of OpenTelemetry Collector provides this integration as the signalfx-forwarder monitor type by using the SignalFx Smart Agent Receiver.

The SignalFx Forwarder receiver runs an HTTP server that listens for data points and trace spans and forwards them to Splunk Observability Cloud. The receiver supports the latest formats for data points and spans that the Splunk ingest API endpoint supports.

This receiver is available on Linux and Windows.

Benefits 🔗

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

  • View metrics using the built-in dashboard. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access Metric Finder and search for metrics sent by the monitor. For information about Metric Finder, see Use the Metric Finder.

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 🔗

This monitor type is available in the Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector. You can use existing Smart Agent monitors as OpenTelemetry Collector metric receivers with the Smart Agent Receiver.

This monitor type requires a properly configured environment on your system in which you’ve installed a functional Smart Agent release bundle. The Collector provides this bundle in the installation paths for x86_64/amd64.

To activate this monitor type in the Collector, add the following lines to your configuration (YAML) file:

receivers:
  smartagent/signalfx-forwarder:
    type: signalfx-forwarder
    ... # Additional config

To complete the receiver activation, you must also include the receiver in both a metrics pipeline and a traces pipeline. To do this, add the receiver to the service > pipelines > metrics (or traces) > receivers section of your configuration file.

For example:

service:
  pipelines:
    metrics:
      receivers: [smartagent/signalfx-forwarder]
    traces:
      receivers: [smartagent/signalfx-forwarder]

Notice 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 receiver:

Option Required Type Description
listenAddress no string 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 127.0.0.1:9080.
serverTimeout no int64 HTTP timeout duration for both read and write operations. Accepts a duration string for https://golang.org/pkg/time/#ParseDuration. The default value is 5s.
sendInternalMetrics no bool 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:

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