Skip to content
For Self-Managed AI Platform users running v11.1, see the on-premise platform documentation

Splunk/SignalFx

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

要件

Splunk tokens for HEC (HTTP Event Collector) and Splunk Observability Cloud (formerly SignalFx) must be populated in the cluster (either by creating it directly in the cluster or using an external secret provider, refer to the External Secrets for DataRobot Kubernetes Installation section in the installation guide). The secrets must be named datarobot-splunk and datarobot-signalfx, respectively, and token saved in the access_token key (for both secrets).

In case it’s being added directly to the cluster, it can be done with the following command:

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

A full working example of the configuration can be found in the datarobot-prime/charts/datarobot-observability-core/examples/splunk.values.yaml file in the DataRobot tarball.

In the minimal configuration without additional custom processors (see extending pipelines with custom processors), the values to update are the following:

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

For additional exporter configuration, check the specific exporter definition where these values are referenced, where a link to the upstream exporter documentation is included.

Once the values are set, DataRobot can be installed/upgraded by specifying the path to this file with the -f option to the helm command.