ClickStack - The ClickHouse Observability Stack

[Edit this page](https://github.com/ClickHouse/clickhouse-docs/blob/main/docs/use-cases/observability/clickstack/overview.md)

**ClickStack** is a production-grade observability platform built on ClickHouse, unifying logs, traces, metrics and session in a single high-performance solution. Designed for monitoring and debugging complex systems, ClickStack enables developers and SREs to trace issues end-to-end without switching between tools or manually stitching together data using timestamps or correlation IDs.

At the core of ClickStack is a simple but powerful idea: all observability data should be ingested as wide, rich events. These events are stored in ClickHouse tables by data type - logs, traces, metrics, and sessions - but remain fully queryable and cross-correlatable at the database level.

ClickStack is built to handle high-cardinality workloads efficiently by leveraging ClickHouse's column-oriented architecture, native JSON support, and fully parallelized execution engine. This enables sub-second queries across massive datasets, fast aggregations over wide time ranges, and deep inspection of individual traces. JSON is stored in a compressed, columnar format, allowing schema evolution without manual intervention or upfront definitions.

## Features[​](#features "Direct link to Features")

The stack includes several key features designed for debugging and root cause analysis:

- Correlate/search logs, metrics, session replays, and traces all in one place
- Schema agnostic, works on top of your existing ClickHouse schema
- Blazing-fast searches & visualizations optimized for ClickHouse
- Intuitive full-text search and property search syntax (ex. `level:err`), SQL optional.
- Analyze trends in anomalies with event deltas
- Set up alerts in just a few clicks
- Dashboard high cardinality events without a complex query language
- Native JSON string querying
- Live tail logs and traces to always get the freshest events
- OpenTelemetry (OTel) supported out of the box
- Monitor health and performance from HTTP requests to DB queries (APM)
- Event deltas for identifying anomalies and performance regressions
- Log pattern recognition

## Components[​](#components "Direct link to Components")

ClickStack consists of three core components:

1. **ClickStack UI (HyperDX)** – a purpose-built frontend for exploring and visualizing observability data
2. **OpenTelemetry collector** – a custom-built, preconfigured collector with an opinionated schema for logs, traces, and metrics
3. **ClickHouse** – the high-performance analytical database at the heart of the stack

These components can be deployed together in a fully **self-managed ClickStack Open Source** setup, or split across managed and self-hosted environments. In **Managed ClickStack**, ClickHouse and the HyperDX UI are hosted and operated in [ClickHouse Cloud](/docs/cloud/get-started), while users run only the OpenTelemetry Collector.

A browser-hosted version of the HyperDX UI is also available, allowing users to connect directly to existing ClickHouse deployments without deploying additional UI infrastructure.

To get started, visit the [Getting started guide](/docs/use-cases/observability/clickstack/getting-started) before loading a [sample dataset](/docs/use-cases/observability/clickstack/sample-datasets). You can also explore documentation on [deployment options](/docs/use-cases/observability/clickstack/deployment) and [production best practices](/docs/use-cases/observability/clickstack/production).

## Principles[​](#clickstack-principles "Direct link to Principles")

ClickStack is designed with a set of core principles that prioritize ease of use, performance, and flexibility at every layer of the observability stack:

### Easy to set up in minutes[​](#clickstack-easy-to-setup "Direct link to Easy to set up in minutes")

ClickStack works out of the box with any ClickHouse instance and schema, requiring minimal configuration. Whether you're starting fresh or integrating with an existing setup, you can be up and running in minutes.

### User-friendly and purpose-built[​](#user-friendly-purpose-built "Direct link to User-friendly and purpose-built")

The HyperDX UI supports both SQL and Lucene-style syntax, allowing users to choose the query interface that fits their workflow. Purpose-built for observability, the UI is optimized to help teams identify root causes quickly and navigate complex data without friction.

### End-to-end observability[​](#end-to-end-observability "Direct link to End-to-end observability")

ClickStack provides full-stack visibility, from front-end user sessions to backend infrastructure metrics, application logs, and distributed traces. This unified view enables deep correlation and analysis across the entire system.

### Built for ClickHouse[​](#built-for-clickhouse "Direct link to Built for ClickHouse")

Every layer of the stack is designed to make full use of ClickHouse's capabilities. Queries are optimized to leverage ClickHouse's analytical functions and columnar engine, ensuring fast search and aggregation over massive volumes of data.

### OpenTelemetry-native[​](#open-telemetry-native "Direct link to OpenTelemetry-native")

ClickStack is natively integrated with OpenTelemetry, ingesting all data through an OpenTelemetry collector endpoint. For advanced users, it also supports direct ingestion into ClickHouse using native file formats, custom pipelines, or third-party tools like Vector.

### Open source and fully customizable[​](#open-source-and-customizable "Direct link to Open source and fully customizable")

ClickStack is fully open source and can be deployed anywhere. The schema is flexible and user-modifiable, and the UI is designed to be configurable to custom schemas without requiring changes. All components—including collectors, ClickHouse, and the UI - can be scaled independently to meet ingestion, query, or storage demands.

## Architectural overview[​](#architectural-overview "Direct link to Architectural overview")

The ClickStack architecture varies depending on how it is deployed. There are important architectural distinctions between **ClickStack Open Source**, where all components are self-managed, and **Managed ClickStack**, where ClickHouse and the HyperDX UI are hosted and operated in ClickHouse Cloud. While the core components remain the same in both models, the responsibility for hosting, scaling, and securing each component differs.

- Managed ClickStack- Open Source ClickStack

Managed ClickStack runs entirely within **ClickHouse Cloud**, providing a fully managed observability backend while preserving the same ClickStack data model and user experience.

In this model, **ClickHouse and the ClickStack UI (HyperDX)** are hosted, operated, and secured by ClickHouse Cloud. Users are responsible only for running an OpenTelemetry Collector to send telemetry data into the managed service.

Managed ClickStack consists of the following components:

1. **ClickStack UI (HyperDX)**  
   The HyperDX UI is fully integrated into ClickHouse Cloud and managed as part of the service. It provides log search, trace exploration, dashboards, alerting, and correlation across telemetry types, with integrated authentication and access control.
2. **OpenTelemetry collector (self-managed)**  
   Users run an OpenTelemetry Collector that receives telemetry data from their applications and infrastructure. This collector forwards data via OTLP to ClickHouse Cloud. While any standards-compliant OpenTelemetry Collector can be used, we strongly recommend the **ClickStack distribution**, which is preconfigured and optimized for ClickHouse ingestion and works out of the box with ClickStack schemas.
3. **ClickHouse Cloud**  
   ClickHouse is fully managed in ClickHouse Cloud, serving as the storage and query engine for all observability data. Users don't need to manage clusters, upgrades, or operational concerns.

Managed ClickStack provides several key benefits: