chmonitorTroubleshooting
Diagnose and fix common chmonitor issues — connection failures, auth errors, performance problems, and Kubernetes probe failures.
Common issues and how to diagnose them, grouped by symptom. Expand the entry that matches what you're seeing.
Connection failures
Auth failures (401 / white screen)
Performance / timeouts
AI agent / LLM failures
Kubernetes / Helm health probes
Related
ClickHouse User & Grants
The least-privilege monitoring user and grants the dashboard needs.
Connection errors
Diagnose 'Test connection' failures kind by kind.
MCP Server — Permissions
Open and secure the MCP endpoint.
Authentication
Compare and configure chmonitor auth providers.
Upgrading ClickHouse
Upgrade safely while chmonitor stays connected.
Zero-signup diagnostics CLI
Run a local, read-only health scan with no chmonitor account.
ClickHouse query optimization
Diagnose and fix slow ClickHouse queries — partition keys, PREWHERE, indices, and memory.
Connection errors
Fix "Test connection" failures in chmonitor — host not allowed, invalid URL, authentication failed, missing permissions, DNS, refused, TLS, and timeout errors.
Fix "Too many parts"
Diagnose and fix ClickHouse's "Too many parts" error — why inserts get throttled, system.parts diagnostic queries, insert batching, and merge-tree tuning.