> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/splunk/using-splunk-otel-collector-with-bindplane.md).

# Using Splunk OTel Collector with Bindplane

Bindplane and the Bindplane Collector can be used to collect data from your [Splunk OTel Collectors](https://docs.splunk.com/observability/en/gdi/opentelemetry/opentelemetry.html).\
This allows you to start taking advantage of Bindplane without the need to re-instrument your\
collectors at the edge.

### Step 1: Deploy a Bindplane Collector as a Gateway

This is the collector you will be routing data through and is what will be managed by Bindplane. In a production environment, this is likely to be a fleet of collectors behind a load balancer. See our [Collector Sizing and Scaling](/production-checklist/bindplane-otel-collector/sizing-and-scaling.md) docs for more details on determining your collector architecture.

### Step 2: Build the Configuration

1. Create a new configuration
2. Add the [OTLP Source](/integrations/sources/opentelemetry-otlp.md).
3. Add a destination of your choice and configure it.

### Step 3: Configure your Splunk OTel Collectors to forward to Bindplane Collector

Modify your Splunk OTel Collector configuration to use an [otlp exporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter). The exporter has many configuration options, see the [readme](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter) for details.

Below is a minimalist configuration example. Replace `bindplane-gateway` with the hostname or IP address of your Bindplane Collector.

```yaml
exporters:
  otlp:
    endpoint: bindplane-gateway:4317
```

Update your pipelines to include the new exporter. This example assumes you have a `traces`, `metrics`, and `logs` pipeline. Your configuration may differ.

```yaml
service:
  pipelines:
    traces:
      exporters:
        - otlp
    metrics:
      exporters:
        - otlp
    logs:
      exporters:
        - otlp
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/how-to-guides/cloud-and-platform-integrations/splunk/using-splunk-otel-collector-with-bindplane.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.