RousselTMLEARNING

Article · ClickStack: from discovery to expertise

Choosing a tool

1. Operating ClickHouse #

Points of attention.

Production #

TopicRecommendation
ReplicationReplicatedMergeTree on at least two replicas, ClickHouse Keeper for coordination
DisksSSD for recent data, object storage (S3) for older data via storage policies
InsertsIn batches (Collector batch processor, or asynchronous inserts): avoid thousands of small inserts
MergesMonitor the number of active parts: too many parts slows everything down
RetentionTTL per table, different per signal (logs 14 d, traces 7 d, metrics 13 months)
-- Santé : parties actives par table et requêtes lentes
SELECT table, count() AS parties FROM system.parts WHERE active GROUP BY table ORDER BY parties DESC LIMIT 5;
SELECT query_duration_ms, substring(query, 1, 80) FROM system.query_log
WHERE type = 'QueryFinish' ORDER BY query_duration_ms DESC LIMIT 5;

2. Choosing #

Depending on the team and existing setup.

Comparison #

CriterionSigNozClickStackGrafana stack (LGTM)Elastic
StorageClickHouseClickHouseObject (Loki, Tempo, Mimir)Elasticsearch
Integrated APM experienceStrongGoodGood (Grafana)Strong
High cardinalityVery goodVery goodLimited in labelsGood
LanguageQuery builder, SQL, PromQLLucene, SQLPromQL, LogQL, TraceQLKQL, ES|QL
Components to operateFew (ClickHouse is the core)FewSeveral databasesAn Elasticsearch cluster
Good practice: If your teams know SQL and need high-cardinality analyses (per customer, per user), a ClickHouse platform is very relevant. If you are already on Grafana, its specialized databases often remain the simplest path.

📄 Operating an observability platform on ClickHouse and choosing a tool →

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

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

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

SigNoz, ClickStack and ClickHouse best practices for observability

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

Observability on ClickHouse: why a columnar database changes the game

Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar ...

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

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

The LGTM stack (Loki, Grafana, Tempo, Mimir): architecture and setup

Grafana Labs' LGTM stack: Loki for logs, Grafana for visualization, Tempo for traces, Mimir for m...

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

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

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

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

Alerts and dashboards in ClickStack

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

Alloy and the Grafana Labs ecosystem: which component for which tool?

The map of Alloy integrations with Faro, Beyla, k6, Loki, Mimir, Tempo, Pyroscope, Database Obser...

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!