Agent skill · data analytics · jeremylongshore
clickhouse-observability
Monitor ClickHouse with Prometheus metrics, Grafana dashboards, system table queries, and alerting for query performance, merge health, and resource usage. Use when setting up ClickHouse monitoring, building Grafana dashboards, or configuring alerts for production ClickHouse deployments. Trigger with "clickhouse monitoring", "clickhouse metrics", "clickhouse Grafana", "clickhouse observability", "monitor clickhouse", "clickhouse Prometheus".
Why this skill is useful
Provides specific Prometheus and Grafana configurations for monitoring ClickHouse that the AI wouldn't reliably generate on its own.
What it needs
Requires grafana, prometheus installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickHouse Observability Overview Set up comprehensive monitoring for ClickHouse using built-in system tables, Prometheus integration, Grafana dashboards, and alerting rules. The workflow layers four signal sources: system. tables (always available, zero dependencies), a Prometheus scrape endpoint, application-level client instrumentation, and alert rules that fire on the failure modes that actually page an on-call — high error rate, latency creep, merge backlog, and resource exhaustion. Deep configs live in references/ so this file stays a fast, followable map. Prerequisites ClickHouse instance with system. table access Prometheus (or compatible: Grafana Alloy, Victoria Metrics) Grafana for dashboards AlertManager or PagerDuty for alerts Instructions Step 1: Query system tables for a health snapshot Start with zero dependencies — the system. tables already hold everything. Run this for an instant server-health read: Query throughput, insert rates, and per-table part counts (the merge-health signal), plus a full table of which system. table to poll at what frequency: system table queries & reference. Step 2: Wire up Prometheus scraping ClickHouse Cloud exposes a managed Prometheus endpoint (Basic auth with a Cloud API key); self-hosted uses the built-in :9363 /metrics endpoint enabled in config.xml. Write the scrape config to your prometheus.yml. Full Cloud + self-hosted scrape configs and the config.xml block: Prometheus scrape config & Grafana dashboards. Step 3: Instrument the application client Server metrics show what ClickHouse does; client metrics attribute latency, error codes, and insert volume to your own code. Wrap queries in a prom-client histogram/counter and expose /metrics. Full instrumentation + structured logging: application-level instrumentation. Step 4: Build Grafana dashboard panels Panels for QPS, P50/P95/P99 latency, error rate, and insert throughput are in the Grafana dashboards reference. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickhouse-observability