1. Operating ClickHouse #
Points of attention.
Production #
| Topic | Recommendation |
|---|---|
| Replication | ReplicatedMergeTree on at least two replicas, ClickHouse Keeper for coordination |
| Disks | SSD for recent data, object storage (S3) for older data via storage policies |
| Inserts | In batches (Collector batch processor, or asynchronous inserts): avoid thousands of small inserts |
| Merges | Monitor the number of active parts: too many parts slows everything down |
| Retention | TTL 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 #
| Criterion | SigNoz | ClickStack | Grafana stack (LGTM) | Elastic |
|---|---|---|---|---|
| Storage | ClickHouse | ClickHouse | Object (Loki, Tempo, Mimir) | Elasticsearch |
| Integrated APM experience | Strong | Good | Good (Grafana) | Strong |
| High cardinality | Very good | Very good | Limited in labels | Good |
| Language | Query builder, SQL, PromQL | Lucene, SQL | PromQL, LogQL, TraceQL | KQL, ES|QL |
| Components to operate | Few (ClickHouse is the core) | Few | Several databases | An 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.
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
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...