> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sending OpenTelemetry to ClickHouse Observability with Bindplane

> Route telemetry to ClickHouse Observability using Bindplane for centralized collector management

Partner Integration

> [!NOTE]
>
> **TL;DR**
>
> This guide shows you how to route telemetry to ClickHouse Observability using Bindplane's native **ClickStack** destination. You'll learn how to:
>
> * Configure ClickHouse Observability as a destination in Bindplane
> * Create a configuration to process and route telemetry
> * Remotely deploy configurations to OTel collectors and start collecting data
> * View telemetry in ClickHouse Observability
>
> Bindplane manages the collectors in your environment and forwards their telemetry to ClickHouse Observability.
>
> Time required: 10-15 minutes

## What is Bindplane?

Bindplane is an OpenTelemetry-native telemetry pipeline that provides centralized management for OpenTelemetry Collectors. It simplifies operating large collector fleets by offering visual configuration editing, safe rollouts, and pipeline intelligence.

## Why Bindplane + ClickHouse Observability?

ClickHouse Observability provides telemetry storage, search, and investigation tools. Bindplane manages the OpenTelemetry Collectors that collect and forward data from your environment.

Bindplane solves this by providing:

* Centralized management for OpenTelemetry Collectors from thousands to over a million
* Visual configuration editing with safe, one-click rollouts
* Automatic resource detection and enrichment applied consistently before data reaches ClickHouse Observability
* Fan-out routing, so the same telemetry streams can be sent to ClickHouse Observability and other destinations simultaneously
* Full pipeline visibility, including collector health, throughput, and end-to-end performance

> [!TIP]
>
> **Key takeaways**
>
> * **ClickHouse Observability stores telemetry and supports investigation**
> * **Bindplane manages the ingestion pipeline and operational complexity of running collector fleets**

## Prerequisites

* A [fully managed ClickHouse Observability service](https://clickhouse.com/docs/clickstack/observability/getting-started.md) or a [self-managed deployment](https://clickhouse.com/docs/clickstack/self-configured/getting-started/managed.md)
* A Bindplane account ([create an account](https://app.bindplane.com))
* An installed Bindplane OTel Collector (see [Install your first collector](https://docs.bindplane.com/readme/install-your-first-collector))
* **Fully managed**: your OTLP HTTP endpoint and ingestion API key from **Team Settings → Data → Managed Telemetry**
* **Self-managed**: a running [standalone collector](https://clickhouse.com/docs/clickstack/self-configured/ingesting-data/collector.md#configuring-the-collector-self-configured), its OTLP endpoint, and the [`OTLP_AUTH_TOKEN`](https://clickhouse.com/docs/clickstack/self-configured/ingesting-data/collector#securing-the-collector-self-configured) configured on it
* Network connectivity from the Bindplane collectors to your OTLP endpoint

## Integrate ClickHouse Observability with Bindplane

**1. Configure ClickHouse Observability as a destination**

In Bindplane, open **Library → Add Destination** and select **ClickStack**. This is the name of Bindplane's destination for sending telemetry to ClickHouse Observability over OTLP.

> [tab] Fully managed
>
> [Beta offering](https://clickhouse.com/docs/reference/settings/beta-and-experimental-features.md#beta-features)
>
> Send telemetry to your managed OTLP endpoint. ClickHouse handles ingestion, schemas, storage, and scaling.
>
> 1. Set **Protocol** to **HTTP**.
> 2. Set **Hostname** to the hostname from your managed OTLP endpoint, without `https://` or the port. For an endpoint such as `https://<service-id>.otel.<region>.aws.clickhouse.com:4318`, enter `<service-id>.otel.<region>.aws.clickhouse.com`.
> 3. Set **Port** to `4318`.
> 4. Set **API Ingestion Key** to `Bearer <YOUR_INGESTION_API_KEY>`, including the `Bearer` prefix. This field supplies the `authorization` header.
> 5. Turn on **Enable TLS** and leave **Skip TLS Certificate Verification** off.
>
> Use the managed OTLP endpoint, not your ClickHouse database endpoint on port `8443`.

> [tab] Self-managed
>
> Send telemetry to the standalone collector connected to your ClickHouse Cloud service. This collector must already be running and [configured to authenticate requests](https://clickhouse.com/docs/clickstack/self-configured/ingesting-data/collector.md#securing-the-collector-self-configured).
>
> 1. Set **Protocol** to **HTTP** or **gRPC**.
> 2. Set **Hostname** to your standalone collector's hostname or IP address, without a URL scheme or port.
> 3. Set **Port** to `4318` for HTTP or `4317` for gRPC, unless you configured a different port.
> 4. Set **API Ingestion Key** to the collector's `OTLP_AUTH_TOKEN` value, without a `Bearer` prefix.
> 5. Set **Enable TLS** to match your collector endpoint. For TLS endpoints, keep certificate verification enabled.

Give the destination a name, such as **Observability production**, then click **Save**. Keep the default gzip compression unless you have verified that your endpoint supports another algorithm.

**2. Create a configuration**

Once your destination is configured, create a configuration to process and route telemetry:

1. Navigate to **Configurations** → **Create Configuration**
2. Give the configuration a name (e.g., "Observability pipeline")
3. Select the **Collector Type** and **Platform** for your deployment
4. Add sources:
   * Click **Add Source** to select from 80+ available sources
   * For testing, you can add a telemetry generator source to simulate traffic
   * For production, add sources for your actual telemetry (logs, metrics, traces)
5. Add your destination:
   * Click **Add Destination**
   * Select the destination you created in the previous step
   * Choose which telemetry types to send (Logs, Metrics, Traces, or all)

> [!TIP]
>
> **Key takeaways**
>
> You can add processors for filtering, sampling, masking, enrichment, batching, and more to shape telemetry before it reaches ClickHouse Observability. This ensures consistent, structured data arrives in ClickHouse.

**3. Add processors (optional)**

Bindplane provides pipeline intelligence and processor recommendations. You can add processors to:

* **Filter**: Reduce data volume by excluding unnecessary telemetry
* **Sample**: Apply sampling strategies to high-volume traces
* **Enrich**: Add resource attributes, labels, or metadata
* **Transform**: Modify telemetry structure or content
* **Batch**: Optimize batch sizes for efficient transmission

These processors are applied consistently across your collector fleet before data reaches ClickHouse Observability.

**4. Deploy collectors and start rollout**

1. Add a collector (BDOT Collector) to your configuration:
   * Navigate to **Collectors** in Bindplane
   * Install the Bindplane collector on your target systems [following Bindplane's installation instructions](https://docs.bindplane.com/readme/install-your-first-collector)
   * The collector will appear in your collector list once connected

2. Assign the configuration to your collectors:
   * Select the collectors you want to use
   * Assign your configuration to them

3. Start a rollout:
   * Click **Start Rollout** to deploy the configuration
   * Bindplane will validate the configuration before rolling it out
   * Monitor the rollout status in the Bindplane UI

> [!TIP]
>
> **Key takeaways**
>
> Bindplane provides safe, one-click rollouts with validation. You can monitor collector health, throughput, and any errors in real-time through the Bindplane interface.

![Telemetry in ClickHouse Observability via Bindplane](https://mintcdn.com/private-7c7dfe99/LCIbqddLfKHZZnfk/images/clickstack/bindplane/bindplane-configuration.webp?fit=max\&auto=format\&n=LCIbqddLfKHZZnfk\&q=85\&s=6341d52afa91e00b1246be04e118ddea)

**5. Verify telemetry in ClickHouse Observability**

Once the configuration is rolled out, telemetry starts flowing into ClickHouse Observability from your managed collector fleet:

1. Open ClickHouse Observability for your service in the ClickHouse Cloud console
2. Search for your services in the **Search** view and use **Chart Explorer** for metrics
3. Confirm that the expected telemetry from your Bindplane-managed collectors has arrived
4. If data is missing, check the Bindplane collector logs for connection or authentication errors

![Telemetry in ClickHouse Observability via Bindplane](https://mintcdn.com/private-7c7dfe99/LCIbqddLfKHZZnfk/images/clickstack/bindplane/bindplane-hyperdx.webp?fit=max\&auto=format\&n=LCIbqddLfKHZZnfk\&q=85\&s=c52b31385e9637aef9ead7a5affb07a1)

## Advanced configuration

### Fan-out routing

Bindplane supports fan-out routing, allowing you to send the same telemetry streams to multiple destinations simultaneously. You can:

* Send logs, metrics, and traces to ClickHouse Observability for long-term storage and analysis
* Route the same data to other observability platforms for real-time alerting
* Forward specific telemetry to SIEM platforms for security analysis

This is configured by adding multiple destinations to your Bindplane configuration.

### Compression and performance

Keep gzip compression enabled to reduce bandwidth usage. Other compression algorithms depend on the protocol and must be supported by the receiving endpoint. For fully managed deployments, use gzip.

## Next steps

Now that you have telemetry flowing from Bindplane to ClickHouse Observability, you can:

* **Build dashboards**: Create visualizations in ClickHouse Observability for logs, metrics, and traces
* **Set up alerts**: Configure alerts in ClickHouse Observability for critical conditions
* **Scale your deployment**: Add more collectors and sources as your observability needs grow
* **Optimize your pipeline**: Use Bindplane's pipeline intelligence to identify optimization opportunities

## Read more

* [ClickStack destination in the Bindplane documentation](https://docs.bindplane.com/integrations/destinations/clickstack)