SignalFx Forwarder 🔗

Description 🔗

The Splunk Distribution of OpenTelemetry Collector provides this integration as the signalfx-forwarder monitor type for the 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. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. 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 the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

Installation 🔗

Follow these steps to deploy this integration:

Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

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

Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Read more on how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
Learn about config options in Collector default configuration.

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.

Get help 🔗

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
- Available to Splunk Observability Cloud customers and free trial users
- To learn how to join, see Get Started with Splunk Community - Chat groups

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

Related Topics