skills.rest
netdata
netdataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

troubleshoot-activemq

Troubleshoots Apache ActiveMQ Classic 5.x failures using Netdata MCP-based diagnostic triage.

1|Updated Apr 17, 2026
Search Tags:#troubleshooting#mcp#observability#gc#dlq#netdata#activemq
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-activemq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot-activemq
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-activemq
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-activemq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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."

Frequently Asked Questions about troubleshoot-activemq

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

FAQPage Schema
How do I troubleshoot ActiveMQ Classic production failures using Netdata?▼

It maps ActiveMQ Classic 5.x incidents into a structured Netdata MCP diagnostic flow by identifying operational failure archetypes like memory pressure cascades, store exhaustion spirals, and KahaDB corruption for targeted remediation.

What causes GC pause death spirals and poison message storms in ActiveMQ?▼

GC pause death spirals and poison message DLQ storms in ActiveMQ are common operational failure archetypes. This Skill diagnoses them by querying Netdata via MCP to find anomalous and correlated metrics over a recent time window.

How do I diagnose KahaDB corruption and store exhaustion in ActiveMQ 5.x?▼

Diagnose KahaDB corruption and store exhaustion spirals in ActiveMQ 5.x by running a structured Netdata MCP-based diagnostic triage that applies the operator playbook to verify where the symptoms originate.

Does this ActiveMQ troubleshooting workflow require specific Netdata MCP alerts?▼

No, this ActiveMQ troubleshooting workflow applies to both real incidents and paged Netdata alert workflows. It uses MCP queries like list_raised_alerts and find_correlated_metrics to confirm symptoms without requiring pre-configured alerts.

What is the best way to identify the dominant failure pattern in an ActiveMQ incident?▼

The best way to identify the dominant failure pattern in an ActiveMQ incident is archetype-driven triage. This approach guides you through likely operational failures and uses Netdata MCP to verify the exact signals to check.

How do I validate ActiveMQ remediation after applying a fix?▼

Validate ActiveMQ remediation by re-querying the same load-bearing activemq.* contexts via Netdata MCP. This confirms signal recovery and ensures the applied fix resolved the memory, store, or connection exhaustion archetype.

Related Skills

Explore More Software Engineering Skills→
netdatanetdata
1

troubleshoot-apache-httpd

Diagnose Apache HTTPD failures by querying Netdata MCP signals.

Official
Advanced
netdatanetdata
1

troubleshoot-cockroachdb

Diagnose CockroachDB incidents by mapping Netdata health signals to failure archetypes.

Official
Advanced
netdatanetdata
1

troubleshoot-mysql

Diagnose MySQL incidents using Netdata signals queried via MCP.

Official
Advanced
netdatanetdata
1

troubleshoot-postgresql

Diagnose PostgreSQL incidents using Netdata MCP queries and structured triage.

Official
Advanced