troubleshoot-clickhouse

What problem does it solve?

It helps you triage and diagnose complex ClickHouse incidents—such as merge debt spirals, memory exhaustion, replication lag cascades, ZooKeeper/Keeper saturation, and disk space collapse—by turning Netdata’s collected signals into a structured diagnostic path.

Core Features & Use Cases

• Failure-mode triage tree: Routes you through the operator playbook’s diagnostic structure mapped to ClickHouse-specific signal domains.
• MCP-driven signal collection: Queries the right Netdata contexts via MCP for liveness, replication availability, parts/merges activity, insert delays/rejections, and error signals.
• Actionable verification loop: Re-runs MCP verification queries after remediation to confirm signals return to expected ranges.
• Use case: An on-call engineer gets paged for a ClickHouse alert and needs a deterministic way to identify the dominant failure archetype and validate remediation.

Quick Start

Use this skill when diagnosing ClickHouse issues by querying Netdata via MCP for the ClickHouse contexts listed in the skill verification section and following the failure archetype decision steps.