1. Why ClickHouse? #
An analytical engine for telemetry.
The strengths of a columnar database #
| Strength | Effect for observability |
|---|---|
| Columnar storage and compression | Highly repetitive logs and traces compressed 10 to 20 times |
| Fast analytical queries | Aggregations over billions of rows in a few seconds |
| High cardinality | No penalty for filtering by user_id or trace_id, unlike a label index |
| SQL | A familiar language, joins between logs, traces and metrics |
| TTL and tiered storage | Automatic retention and moving data to object storage |
Good to know: ClickHouse is an open source database (Apache 2.0) created at Yandex and now developed by ClickHouse Inc.
2. The landscape #
Several products on the same database.
The tools #
| Tool | Type | Strengths |
|---|---|---|
| SigNoz | Complete platform (APM, logs, metrics, alerts) | Experience close to a commercial APM, native OpenTelemetry |
| ClickStack | ClickHouse's official stack: ClickHouse + HyperDX + Collector | Fast search, correlation, browser sessions |
| Uptrace | APM on ClickHouse | Traces and metrics, easy to deploy |
| Grafana + ClickHouse plugin | Visualization | Fits into an existing Grafana stack |
Good practice: All these tools receive OTLP: by instrumenting with OpenTelemetry, you can switch interfaces without touching the applications.
3. Comparing with other approaches #
Index, labels or columns.
Three families #
| Approach | Examples | Strength | Weakness |
|---|---|---|---|
| Inverted index | Elasticsearch, OpenSearch | Full-text search | Cost of storage and indexing |
| Labels + object storage | Loki, Tempo, Mimir | Very low cost | Limited high cardinality in labels |
| Columnar database | ClickHouse (SigNoz, ClickStack) | Analytics and high cardinality | A database to operate (replication, merges, disks) |
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
SigNoz, ClickStack and ClickHouse best practices for observability
Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...
Operating an observability platform on ClickHouse and choosing a tool
Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...
ClickStack: architecture, components and offerings (ClickHouse, HyperDX, OpenTelemetry)
ClickStack, ClickHouse's official observability stack: role of ClickHouse, the UI (HyperDX), the ...
Telemetry in ClickHouse: schema, SQL, materialized views and retention
Telemetry in ClickHouse: otel_logs, otel_traces, otel_metrics_* and hyperdx_sessions tables, sort...
The observability trilemma: cost, completeness and performance, and how solutions resolve it
Understanding the observability trilemma (cost, data completeness, query performance), its three ...
Operating ClickHouse for ClickStack: sizing, replication, monitoring, security and backup
Running ClickHouse in production for observability: estimating volume and disk, replicating with ...
Alerts and dashboards in ClickStack
Building charts and dashboards in ClickStack, creating alerts on a search or a chart, sending the...
Exploring with the ClickStack UI: sources, search, traces, sessions and SQL
Using the ClickStack UI (HyperDX): data sources, property and full-text search syntax, SQL mode, ...
Using SigNoz: APM, traces, logs, dashboards and alerts
Use SigNoz day to day: APM view of services, traces and logs explorers, query builder, ClickHouse...