# Splunk Observability Cloud

### Supported Types

| Metrics | Logs | Traces |
| ------- | ---- | ------ |
| ✓       | ✓    | ✓      |

### Configuration Table

<table><thead><tr><th width="146.28515625">Parameter</th><th width="187.125">Type</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>telemetry_types</td><td><code>telemetrySelector</code></td><td><code>['Logs', 'Metrics', 'Traces']</code></td><td>The types of telemetry data to send to Splunk Observability Cloud. Valid values are: <code>Logs</code>, <code>Metrics</code>, and <code>Traces</code>.</td></tr><tr><td>token*</td><td><code>string</code></td><td></td><td>Token used to authenticate with the Splunk (SignalFx) metric, trace, and log APIs</td></tr><tr><td>realm</td><td><code>enum</code></td><td>us0</td><td>The Splunk API realm (region) to use when sending metrics, traces, and logs. Valid values are: <code>us0</code>, <code>us1</code>, <code>us2</code>, <code>eu0</code>, or <code>jp0</code>.</td></tr></tbody></table>

<mark style="color:red;">\*</mark>*<mark style="color:red;">required field</mark>*

### Supported Retry and Queuing Settings

This destination supports the [retry settings](https://docs.bindplane.com/configuration/bindplane-otel-collector/retry-on-failure), the [sending queue settings](https://docs.bindplane.com/configuration/bindplane-otel-collector/sending-queue), and the [persistent queue settings.](https://docs.bindplane.com/configuration/bindplane-otel-collector/persistent-queue)

| Sending Queue | Persistent Queue | Retry on Failure |
| ------------- | ---------------- | ---------------- |
| ✓             | ✓                | ✓                |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/integrations/destinations/splunk-observability-cloud.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.