troubleshoot-rabbitmq

To troubleshoot RabbitMQ throughput degradation, the Skill queries Netdata via MCP to correlate host and service signals, routing diagnostics through operator playbook domains like backpressure, resource alarms, and queue depth to identify root causes.

The best way to triage RabbitMQ availability incidents is using a structured signal-driven diagnostic path that queries Netdata for anomalous metrics and raised alerts, mapping them to specific RabbitMQ operator playbook domains for targeted remediation.

RabbitMQ throttling and resource alarms occur when system limits are hit, diagnosable by querying Netdata metrics via MCP to find anomalous metrics and raised alerts, then correlating host and service signals to pinpoint the exact resource constraint.

Yes, you can use Netdata MCP queries like list_nodes, query_metrics, find_anomalous_metrics, and list_raised_alerts to diagnose RabbitMQ errors, replacing guesswork with correlated host and service observability data.

To verify RabbitMQ incident remediation, re-run the same MCP queries on the affected contexts to confirm the original anomalous metrics and raised alerts have cleared, ensuring the fix resolved the incident rather than merely changing the symptom.