---
title: "bitdrift brings ClickHouse-powered mobile observability to ClickStack"
description: "bitdrift has joined ClickHouse’s House Mates program as a mobile observability partner, bringing mobile-native telemetry, tracing, and debugging to ClickStack. ClickStack provides an open-source or managed observability stack built on ClickHouse, with HyperDX and an OpenTelemetry Collector for logs, metrics, traces, and OTLP ingestion. bitdrift’s Capture SDK supports iOS, Android, and React Native, stores unsampled telemetry in a fixed-size on-device ring buffer, and uses control-plane configuration to decide what is collected or uploaded. Shared OpenTelemetry trace context lets engineers follow a mobile request’s trace ID from a session timeline into ClickStack, where backend traces, dependencies, logs, metrics, database operations, and infrastructure behavior are available, creating a continuous debugging path across the device and distributed systems."
---

# bitdrift brings ClickHouse-powered mobile observability to ClickStack

[Clickhouse](https://yomu.fyi/company/clickhouse) · Aug 11, 2026

**Type:** Announcement

## Summary

bitdrift has joined ClickHouse’s House Mates program as a mobile observability partner, bringing mobile-native telemetry, tracing, and debugging to ClickStack. ClickStack provides an open-source or managed observability stack built on ClickHouse, with HyperDX and an OpenTelemetry Collector for logs, metrics, traces, and OTLP ingestion. bitdrift’s Capture SDK supports iOS, Android, and React Native, stores unsampled telemetry in a fixed-size on-device ring buffer, and uses control-plane configuration to decide what is collected or uploaded. Shared OpenTelemetry trace context lets engineers follow a mobile request’s trace ID from a session timeline into ClickStack, where backend traces, dependencies, logs, metrics, database operations, and infrastructure behavior are available, creating a continuous debugging path across the device and distributed systems.

## Context

Most observability platforms focus on servers, containers, and short-lived backend requests, while mobile sessions can run for hours, move across networks, go offline, encounter device-specific limits, and produce more diagnostic context than can be streamed continuously. Traditional mobile tools may sample away the session needed to diagnose an issue.

## Approach / What changed

The integration combines bitdrift Capture’s on-device, unsampled telemetry and selective upload model with ClickStack’s ClickHouse-backed, OpenTelemetry-native observability stack. Shared trace IDs connect mobile network requests to backend traces; Android uses bitdrift’s OkHttp tracing integrations, while iOS uses the existing URLSession integration.

## Takeaways

- bitdrift Capture stores mobile telemetry in a fixed-size ring buffer on the device and uploads selected data through real-time control-plane configuration.
- OpenTelemetry trace context connects a request’s trace ID from a bitdrift mobile session timeline to its distributed backend trace in ClickStack.
- ClickStack’s ClickHouse storage and parallel query engine are intended for high-cardinality observability workloads such as large volumes of traces and application logs.

**Tags:** [Android](https://yomu.fyi/topic/android), [iOS](https://yomu.fyi/topic/ios), [Monitoring](https://yomu.fyi/topic/monitoring), [Open Source](https://yomu.fyi/topic/open-source), [Performance](https://yomu.fyi/topic/performance)

- Source: [Clickhouse](https://clickhouse.com/blog/bitdrift-clickhouse-mobile-observability-for-clickstack)
- Source URL: https://clickhouse.com/blog/bitdrift-clickhouse-mobile-observability-for-clickstack
- Ingested by Yomu: 2026-08-29T07:45:57.584Z

[Read original post](https://clickhouse.com/blog/bitdrift-clickhouse-mobile-observability-for-clickstack)