Home / Articles
Observability
SigNoz, ClickStack and ClickHouse best practices for observability Production checklist for an observability platform on ClickHouse: OpenTelemetry instrumentation, batched ingestion, retention, replication, security and costs.
Martin LEKPA 3 min read Published 19/10/2026 Updated 08/11/2026
1. Collecting # OpenTelemetry first.
Principles # OpenTelemetry instrumentation only: the interface stays replaceable. service.name, service.version and deployment.environment everywhere.Collectors with the batch processor and a memory limit. Trace sampling (tail sampling) beyond a few thousand spans per second. 2. Storing # ClickHouse operated well.
Rules # Per-signal retention with TTL. Replication and backups (BACKUP to S3). Tiered storage for old data. Monitoring of parts, merges and slow queries. Separate ClickHouse accounts for ingestion and reading. Reference diagram and quick check # Checklist.
Checklist # Applications instrumented with OpenTelemetry Collectors sized Replicated ClickHouse with TTL Alerts on critical services Tested backups Authenticated access to the interface
Martin LEKPA Tech Lead et formateur Observabilité
Web →
Related articles Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar storage, com…
SigNoz components (OpenTelemetry collector, ClickHouse, query service, interface, alerts), installation with …
Use SigNoz day to day: APM view of services, traces and logs explorers, query builder, ClickHouse and PromQL …
Get new articles and courses A weekly or monthly digest, as you prefer, only when there is something new. Unsubscribe in one click.
×
♥ 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.
Or scan this QR code with your phone
Thank you, every contribution counts!