Skip to main content

Signalfx Receiver

Status Available in: contrib Maintainers: @dmitryax Source: opentelemetry-collector-contrib

Supported Telemetry

Logs Metrics

Overview

The SignalFx receiver accepts:

Configuration

The following settings are required:
  • endpoint (default = localhost:9943): Address and port that the SignalFx receiver should bind to. See our security best practices doc to understand how to set the endpoint in different environments.
The following settings are optional:
  • tls_settings (no default): This is an optional object used to specify if TLS should be used for incoming connections. Both key_file and cert_file are required to support incoming TLS connections.
    • cert_file: Specifies the certificate file to use for TLS connection.
    • key_file: Specifies the key file to use for TLS connection.
Example:
receivers:
  signalfx:
  signalfx/advanced:
    tls:
      cert_file: /test.crt
      key_file: /test.key
The full list of settings exposed for this receiver are documented in config.go with detailed sample configurations in testdata/config.yaml.
:warning: When enabling the SignalFx receiver or exporter, configure both the metrics and logs pipelines.
service:
  pipelines:
    metrics:
      receivers: [signalfx]
      processors: [memory_limiter]
      exporters: [signalfx]
    logs:
      receivers: [signalfx]
      processors: [memory_limiter]
      exporters: [signalfx]

Access token passthrough

Access token passthrough is no longer supported, to achieve similar behavior configure your collector to use the headers_setter extension to pass the access token.

Configuration

Example Configuration

signalfx:
signalfx/allsettings:
  # endpoint specifies the network interface and port which will receive
  # SignalFx metrics.
  endpoint: localhost:9943
signalfx/tls:
  tls:
    cert_file: /test.crt
    key_file: /test.key

Last generated: 2026-04-13