RousselTMLEARNING

Article · SigNoz: from discovery to expertise

Observability on ClickHouse

1. Why ClickHouse? #

An analytical engine for telemetry.

The strengths of a columnar database #

Observability stack on ClickHouse
A single storage engine and a single language (SQL) for all signals.
StrengthEffect for observability
Columnar storage and compressionHighly repetitive logs and traces compressed 10 to 20 times
Fast analytical queriesAggregations over billions of rows in a few seconds
High cardinalityNo penalty for filtering by user_id or trace_id, unlike a label index
SQLA familiar language, joins between logs, traces and metrics
TTL and tiered storageAutomatic 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 #

ToolTypeStrengths
SigNozComplete platform (APM, logs, metrics, alerts)Experience close to a commercial APM, native OpenTelemetry
ClickStackClickHouse's official stack: ClickHouse + HyperDX + CollectorFast search, correlation, browser sessions
UptraceAPM on ClickHouseTraces and metrics, easy to deploy
Grafana + ClickHouse pluginVisualizationFits 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 #

ApproachExamplesStrengthWeakness
Inverted indexElasticsearch, OpenSearchFull-text searchCost of storage and indexing
Labels + object storageLoki, Tempo, MimirVery low costLimited high cardinality in labels
Columnar databaseClickHouse (SigNoz, ClickStack)Analytics and high cardinalityA database to operate (replication, merges, disks)

📄 Observability on ClickHouse: why a columnar database changes the game →

My progress

  • ⏱ Estimated time : ≈ 3 min

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.

Ask a question about this lesson →

Recommended Articles

SigNoz, ClickStack and ClickHouse best practices for observability

Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...

ClickStack: architecture, components and offerings (ClickHouse, HyperDX, OpenTelemetry)

ClickStack, ClickHouse's official observability stack: role of ClickHouse, the UI (HyperDX), the ...

Operating an observability platform on ClickHouse and choosing a tool

Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...

The observability trilemma: cost, completeness and performance, and how solutions resolve it

Understanding the observability trilemma (cost, data completeness, query performance), its three ...

Telemetry in ClickHouse: schema, SQL, materialized views and retention

Telemetry in ClickHouse: otel_logs, otel_traces, otel_metrics_* and hyperdx_sessions tables, sort...

Using SigNoz: APM, traces, logs, dashboards and alerts

Use SigNoz day to day: APM view of services, traces and logs explorers, query builder, ClickHouse...

SigNoz: architecture and installation

SigNoz components (OpenTelemetry collector, ClickHouse, query service, interface, alerts), instal...

Alerts and dashboards in ClickStack

Building charts and dashboards in ClickStack, creating alerts on a search or a chart, sending the...

Operating ClickHouse for ClickStack: sizing, replication, monitoring, security and backup

Running ClickHouse in production for observability: estimating volume and disk, replicating with ...

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!