troubleshoot-zookeeper

Diagnose Apache ZooKeeper incidents via Netdata MCP metrics and remediation verification.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-zookeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-zookeeper
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-zookeeper
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-zookeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps diagnose Apache ZooKeeper failures by mapping common incident archetypes (quorum loss, write stalls, GC pause cascades, session storms, heap/OOM, and snapshot stalls) to the exact Netdata signals you need, using MCP queries for structured triage and remediation recommendations.

Core Features & Use Cases

  • Operator-playbook diagnostic tree: Routes a coding agent through ZooKeeper health domains (availability, latency, throughput, connections/sessions, replication/sync, data tree/memory, errors/integrity, JVM/resources, security) to narrow root cause.
  • MCP-based signal verification: Performs discovery and verification via list_metrics, query_metrics, and anomaly ranking via find_anomalous_metrics against the relevant zookeeper.* contexts.
  • Remediation confirmation loop: Re-runs the same MCP verification queries after applying remediation to confirm signals return to expected ranges.

Quick Start

Ask an AI agent to troubleshoot your Apache ZooKeeper with Netdata using MCP by querying the ZooKeeper zookeeper.* contexts for the last 15 to 30 minutes, selecting the correct failure archetype, then applying the remediation and verifying the signals recover.

Frequently Asked Questions about troubleshoot-zookeeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot ZooKeeper quorum loss using Netdata?

Troubleshoot ZooKeeper quorum loss by querying Netdata `zookeeper.*` metrics via MCP to detect availability drops, then follow the operator-playbook diagnostic tree to pinpoint the failed ensemble nodes and verify recovery.

What causes ZooKeeper session expiration storms and how can I diagnose them?

Diagnose ZooKeeper session expiration storms by querying Netdata connection and session metrics through MCP, applying the diagnostic tree to identify GC pause cascades or heap exhaustion triggering the session timeouts.

How do I fix ZooKeeper write pipeline stalls and snapshot stalls?

Fix ZooKeeper write pipeline stalls and snapshot stalls by using Netdata MCP to query latency and sync metrics, applying the playbook-mapped diagnostic tree to isolate replication bottlenecks, and verifying post-remediation signal recovery.

Can I use Netdata MCP to diagnose JVM garbage collection pauses affecting ZooKeeper?

Use Netdata MCP to diagnose JVM garbage collection pauses affecting ZooKeeper by querying JVM resource metrics and `zookeeper.*` contexts, then ranking anomalous metrics to confirm GC cascade impacts on availability.

Does this ZooKeeper troubleshooting approach require specific dependencies?

This ZooKeeper troubleshooting approach requires no external dependencies, relying solely on Netdata MCP queries like `list_metrics`, `query_metrics`, and `find_anomalous_metrics` against ZooKeeper contexts for structured triage.

What is the best way to verify ZooKeeper remediation after applying a fix?

Verify ZooKeeper remediation by re-running the same Netdata MCP verification queries against the affected `zookeeper.*` contexts to confirm that health signals have returned to their expected ranges.