Splunk/SignalFx¶

This section shows how to configure the chart to export telemetry to Splunk (logs) and SignalFx (metrics and traces).

要件¶

Kubernetes secrets containing the Splunk HEC (HTTP Event Collector) token and the Splunk Observability Cloud (formerly SignalFx) token must exist in the cluster (either by creating them directly or using an external secret provider, refer to the External Secrets for DataRobot Kubernetes Installation section in the installation guide). The secret names and keys are configurable - they just need to match what is referenced in the secrets section of the chart configuration below.

To add the secrets directly to the cluster, use the following commands:

kubectl create secret -n <DR_CORE_NAMESPACE> generic datarobot-splunk \
  --from-literal=access_token="<HEC_ACCESS_TOKEN>"

kubectl create secret -n <DR_CORE_NAMESPACE> generic datarobot-signalfx \
  --from-literal=access_token="<SIGNALFX_ACCESS_TOKEN>" 

Full chart configuration¶

The following configuration is added to the datarobot-prime chart values. Replace the placeholder values with the actual values.

For additional exporter configuration options, refer to the upstream OpenTelemetry documentation for the splunkhec and signalfx exporters.

global:
  observability:
    secrets:
      - envVar: SPLUNK_HEC_TOKEN
        secretName: datarobot-splunk
        secretKey: access_token
      - envVar: SIGNALFX_TOKEN
        secretName: datarobot-signalfx
        secretKey: access_token

    exporters:
      splunk_hec:
        token: ${env:SPLUNK_HEC_TOKEN}
        endpoint: <SPLUNK_HEC_ENDPOINT>
        source: datarobot
        sourcetype: _json
      signalfx:
        access_token: ${env:SIGNALFX_TOKEN}
        realm: <SIGNAL_FX_REALM>
        api_url: https://api.<SIGNAL_FX_REALM>.signalfx.com
        ingest_url: https://ingest.<SIGNAL_FX_REALM>.signalfx.com

    signals:
      logs:
        exporters: [splunk_hec]
      metrics:
        exporters: [signalfx]
      traces:
        exporters: [signalfx] 

各パラメーターについて説明します。

• <SPLUNK_HEC_ENDPOINT>: the HEC endpoint, refer to the official Splunk cloud/ enterprise docs to retrieve this endpoint
• <SIGNAL_FX_REALM>: the SignalFx realm (e.g. us1)

The secrets section injects the SPLUNK_HEC_TOKEN and SIGNALFX_TOKEN environment variables from their respective Kubernetes secrets into all collector pods. The exporters reference these values using the ${env:VAR_NAME} syntax.