SignalFx receiver

The SignalFx receiver collects metrics and logs in SignalFx proto format.

The SignalFx receiver is a native OpenTelemetry component that allows the Splunk Distribution of the OpenTelemetry Collector to collect data in SignalFx proto format. This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector in the metrics and logs/signalfx pipelines when you deploy the collector in host monitoring (agent) mode.

Supported pipeline types are metrics and logs. See Process your data with pipelines for more information.

The SignalFx receiver accepts:

Metrics in the SignalFx proto format. For more information, see SignalFx metrics protobuf .
Events (logs) in the SignalFx proto format. For more information, see Send Traces, Metrics, and Events in the Splunk Developer Program documentation.

Deploy the collector

See Deploy the Splunk Distribution of the OpenTelemetry Collector.

Configure the receiver

Edit the OpenTelemetry Collector configuration file to add the SignalFx receiver:

Add signalfx to the receivers section of your OpenTelemetry Collector configuration file.
Tip: The old method for passing your access token through the access_token_passthrough parameter is deprecated. Replace this method with either the headers_setter extension or the combination of include_metadata: true and the batch processor. The latter is the recommended method because it ensures that the access token used by default is what the receiver sends. Both methods are illustrated below.
Default configuration
CAUTION: Don't remove the signalfx receiver from the default configuration. If you need to change its settings, use the existing receiver or create a separate receiver configuration.
```
receivers:
  signalfx:
    endpoint: 0.0.0.0:9943
```
Separate configuration with headers_setter
Use header_setter extension to pass through specific key-value pairs (such as your access token) in the receiver's HTTP response headers.
```
extensions:
  headers_setter:
    headers:
      - action: upsert
        key: X-SF-TOKEN
        from_context: X-SF-TOKEN
        default_value: "${SPLUNK_OBSERVABILITY_ACCESS_TOKEN}"

receivers:
  signalfx: null
  signalfx/allsettings:
    endpoint: 'localhost:9943'
    
  signalfx/tls:
    tls:
      cert_file: /test.crt
      key_file: /test.key
```
Separate configuration with include_metadata and the batch processor
Use the include_metadata: true parameter combined with the batch processor as shown in the example below.
```
receivers:
  signalfx: null
  signalfx/allsettings:
    endpoint: 0.0.0.0:9943
    include_metadata: true
  signalfx/tls:
    tls:
      cert_file: /test.crt
      key_file: /test.key

processors:
  batch:
    metadata_keys:
      - X-SF-Token
```
Configure advanced settings.

Add the signalfx to both the metrics and logs pipelines, in both the receivers and the exporters arrays:

service:
  pipelines:
    metrics:
      receivers: [signalfx]
      processors: [memory_limiter, batch]
      exporters: [signalfx]
    logs:
      receivers: [signalfx]
      processors: [memory_limiter, batch]
      exporters: [signalfx]

Restart the collector

To apply your configuration changes, restart the collector. The command to restart the Splunk Distribution of the OpenTelemetry Collector varies depending on what platform you deployed it on and what tool you used to deploy it, but here are general examples of the restart command:

Linux with installer script:

sudo systemctl restart splunk-otel-collector

Windows with installer script:

stop-service splunk-otel-collector
start-service splunk-otel-collector

Kubernetes with Helm:

sudo systemctl restart splunk-otel-collector

Settings

The following table shows the configuration options for the SignalFx receiver:

CAUTION: If you use the access_token_passthrough setting with any exporter other than the SignalFx exporter, the receiver might reveal all organization access tokens. If you activate this setting, you must use the SignalFx receiver with the SignalFx exporter.

included

https://raw.githubusercontent.com/splunk/collector-config-tools/main/cfg-metadata/receiver/signalfx.yaml

Metrics

The following metrics, resource attributes, and attributes, are available.

included

https://raw.githubusercontent.com/splunk/collector-config-tools/main/metric-metadata/signalfxreceiver.yaml

特定のメトリクスをアクティブまたは非アクティブにする

各メトリクスの metrics セクションの enabled フィールドを設定することで、特定のメトリクスをアクティブまたは非アクティブにできます。例：

receivers:
  samplereceiver:
    metrics:
      metric-one:
        enabled: true
      metric-two:
        enabled: false

以下は、アクティブ化されたメトリクスを持つホスト・メトリクス・レシーバーの構成例です：

receivers:
  hostmetrics:
    scrapers:
      process:
        metrics:
          process.cpu.utilization:
            enabled: true

Note: 非アクティブ化されたメトリックは Splunk Observability Cloud に送信されません。

請求

MTS ベースのサブスクリプションの場合、すべてのメトリックがメトリックの使用にカウントされます。
ホストベースのプランを使用している場合、このドキュメントでアクティブ（アクティブ：はい）としてリストされているメトリックはデフォルトと見なされ、無料で含まれています。

詳細については、「Infrastructure Monitoringのサブスクリプション使用状況（ホストとメトリクスのプラン）」を参照してください。

Troubleshooting

__ ___ ___ _ ______ _____________ _____ ________ ___ ___ ___ ____ __ ___ ____ ____ __ ______ _____________ ______ ___ ___ ___ ____ __ ___ _________ _____

_________ __ ______ _____________ _____ _________

______ _ ____ __ ___ ______ _______ _______
_______ ______ ________

_________ __ ___________ _________ ___ ____ _____ _____

___ _ ________ ___ ___ _______ _______ _________ _______ __ ______ ________
____ ___ ______ ______________ ____ _____ _____ _______ __ ___________ ____ __________ _________ ___ ______ _________ __________ __ _____ ___ ____ _______