troubleshoot-activemq

What problem does it solve?

Troubleshoots Apache ActiveMQ Classic 5.x incidents by mapping common failure archetypes—memory pressure cascades, store exhaustion spirals, GC pause death spirals, poison message/DLQ storms, connection/thread exhaustion, and KahaDB corruption—into a structured Netdata/MCP diagnostic flow.

Core Features & Use Cases

• Archetype-driven triage: Guides an agent through the most likely operational failure patterns and what to verify first.
• Netdata MCP health signal verification: Uses MCP queries (list_nodes, query_metrics, find_anomalous_metrics, find_correlated_metrics, list_raised_alerts) to confirm where the symptoms originate.
• Operator playbook alignment: Applies the Netdata operator playbook diagnostic tree, then recommends remediation and validates signal recovery after changes.
• Use case: An on-call engineer is paged on a Netdata alert tied to an ActiveMQ instance and needs a repeatable root-cause workflow rather than ad-hoc dashboard checking.

Quick Start

Ask your agent: "Use netdata MCP to troubleshoot my Apache ActiveMQ Classic 5.x instance for the most likely failure pattern and tell me what signals to check and what remediation to apply."