# 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](https://docs.bindplane.com/how-to-guides/broken-reference) docs for more details on determining your collector architecture.

### Step 2: Build the Configuration

1. Create a new configuration
2. Add the [OTLP Source](https://bindplane.com/docs/resources/sources/opentelemetry).

<figure><img src="https://content.gitbook.com/content/A6BP9V0wfJj4LZdQH6OJ/blobs/dstD2FWw42yDYeAtiFGb/how-to-guides-using-splunk-otel-collector-with-bindplane-image-1%20(1).png" alt="Bindplane docs - Using Splunk OTEL Collector with Bindplane - image 1"><figcaption></figcaption></figure>

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
```