> ## Documentation Index
> Fetch the complete documentation index at: https://docs.odigos.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Splunk (SAPM) (Deprecated)
> Configuring the Splunk (SAPM) (Deprecated) backend (Managed)
### Getting Started
**Obtaining Access Token**
Go to **Settings** then **Access Tokens** and click **Create New Token**
Give the token a name and select **Ingest Token** for the authorization scope and click create.
### Configuring Destination Fields
✅ Traces
❌ Metrics
❌ Logs
❌ Profiles
* **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](https://docs.odigos.io/cli/odigos_ui) to access the UI
```bash theme={null}
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. `splunk.yaml`)
```yaml theme={null}
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
name: splunk-example
namespace: odigos-system
spec:
data:
SPLUNK_REALM:
destinationName: splunk
secretRef:
name: splunk-secret
signals:
- TRACES
type: splunk
---
apiVersion: v1
data:
SPLUNK_ACCESS_TOKEN:
kind: Secret
metadata:
name: splunk-secret
namespace: odigos-system
type: Opaque
```
Apply the YAML using `kubectl`
```bash theme={null}
kubectl apply -f splunk.yaml
```