Splunk (SAPM) (Deprecated)

Getting Started

Configuring Destination Fields

Supported Signals:

✅ Traces ❌ Metrics ❌ Logs

SPLUNK_ACCESS_TOKEN string : Access Token.
- This field is required
SPLUNK_REALM string : Realm. The Splunk realm in use. This is the second part of the URL you use to access Splunk/SignalFX. For example, if you access Splunk at https://app.us1.signalfx.com, then the realm is us1.
- This field is required

Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

Using the UI

Use the Odigos CLI to access the UI

odigos ui

Click on Add Destination, select Splunk (SAPM) (Deprecated) and follow the on-screen instructions

Using Kubernetes manifests

Save the YAML below to a file (e.g. splunksapm.yaml)

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: splunksapm-example
  namespace: odigos-system
spec:
  data:
    SPLUNK_REALM: <Realm>
  destinationName: splunksapm
  secretRef:
    name: splunksapm-secret
  signals:
  - TRACES
  type: splunksapm

---

apiVersion: v1
data:
  SPLUNK_ACCESS_TOKEN: <Base64 Access Token>
kind: Secret
metadata:
  name: splunksapm-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f splunksapm.yaml

Getting Started

Odigos AI

Instrumentations

Odigos Pipeline

Destinations

Concepts

Authentication

Contribution Guidelines

Splunk (SAPM) (Deprecated)

Getting Started

Configuring Destination Fields

Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos