troubleshoot-elasticsearch

What problem does it solve?

Elasticsearch incidents often cascade from specific resource or configuration failure archetypes, but generic checks miss the true cause and lead to slow, incorrect remediation.

Core Features & Use Cases

• Structured triage for Elasticsearch failure archetypes: Covers heap pressure death spirals, shard overallocation, disk watermark cascades, mapping explosions, merge storms, and master instability.
• Netdata + MCP signal-driven diagnosis: Queries Netdata via MCP for Elasticsearch health signals and follows the Netdata operator playbook diagnostic tree.
• Remediation validation: Re-runs the same MCP verification queries to confirm signals return to expected ranges and flags when the fix does not hold.

Use case: an on-call engineer is paged by a Netdata alert for a specific Elasticsearch node and needs a reliable, step-by-step path to determine whether the incident is driven by heap pressure, shard bloat, disk watermarks, mapping growth, indexing/merge backlog, or master overwhelm.

Quick Start

Use the troubleshoot-elasticsearch skill to diagnose my Elasticsearch incident using Netdata MCP signals and recommend the most likely remediation.