> ## Documentation Index
> Fetch the complete documentation index at: https://otel.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# Signalfx

> OpenTelemetry receiver for Signalfx

# Signalfx Receiver

![Status](https://img.shields.io/badge/status-deprecated-lightgrey)

**Available in:** `contrib`

**Maintainers:** [@dmitryax](https://github.com/dmitryax)

**Source:** [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/signalfxreceiver)

## Supported Telemetry

![Logs](https://img.shields.io/badge/logs-deprecated-blue) ![Metrics](https://img.shields.io/badge/metrics-deprecated-green)

## Overview

The SignalFx receiver accepts:

* Metrics in the [SignalFx proto
  format](https://github.com/signalfx/com_signalfx_metrics_protobuf).
* Events (Logs) in the [SignalFx proto
  format](https://github.com/signalfx/com_signalfx_metrics_protobuf/blob/master/proto/signalfx_metrics.proto#L137).
  More information about sending custom events can be found in the [SignalFx
  Developers
  Guide](https://dev.splunk.com/observability/reference/api/ingest_data/latest).

## 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](https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks) 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:

```yaml theme={null}
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](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/signalfxreceiver/config.go)
with detailed sample configurations in [testdata/config.yaml](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/signalfxreceiver/testdata/config.yaml).

> :warning: When enabling the SignalFx receiver or exporter, configure both the `metrics` and `logs` pipelines.

```yaml theme={null}
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

```yaml theme={null}
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-07-06*