---
title: ClickHouse
---
# ClickHouse

bitdrift is an integration partner for ClickHouse, connecting mobile-native telemetry to [ClickStack](https://clickhouse.com/docs/use-cases/observability/clickstack/overview){:target="_blank"}, ClickHouse's open source observability stack.

## What is ClickStack?

ClickStack has three core components:

- **ClickHouse**, the column-oriented database that stores and queries observability data.
- **ClickStack UI (HyperDX)**, for searching, visualizing, correlating, and alerting on that data.
- **OpenTelemetry Collector**, for receiving logs, metrics, and traces over OTLP.

## How bitdrift and ClickStack work together

- **bitdrift** captures what happened on the device: user actions, app state, network requests, logs, errors, crashes, and performance signals.
- **ClickStack** captures what happened once a request reached the backend: distributed traces, service dependencies, logs, metrics, and infrastructure behavior.
- **OpenTelemetry trace context** ties the two together.

From a network request in a bitdrift Timeline, an engineer can follow the trace ID into the ClickStack UI (HyperDX) and see the request move across backend services, without lining up timestamps across two disconnected tools.

## Configure tracing

This integration is built on bitdrift's [Tracing](../../sdk/features/tracing.md) feature. See that page for full setup details, availability requirements, and supported trace propagation formats (`w3c`, `b3-single`, `b3-multi`).

At a high level:

1. Ask bitdrift Support to [enable tracing](../../support/contact.md) for your tenant, and configure trace deep linking to your ClickStack (HyperDX) instance.
2. Enable bitdrift's network integration for your platform so tracing headers are propagated on outgoing requests. See [Tracing > Network integration](../../sdk/features/tracing.md#network-integration) for the Android and iOS setup steps.
3. Add a **Start Tracing** [workflow action](../workflows/actions.md#start-tracing) to turn on tracing for matching sessions.

Once configured, bitdrift Timeline log rows and span views show a **View Trace** link that carries the captured trace ID into ClickStack.

!!! info "Availability"
    Tracing is an experimental feature and is not enabled for all tenants by default. [Contact us](../../support/contact.md) if you want tracing enabled for your tenant.