troubleshoot-rabbitmq

Name: troubleshoot-rabbitmq
Availability: InStock
Author: netdata

Diagnose RabbitMQ availability and throughput issues using Netdata MCP queries.

1|Updated Apr 17, 2026

Search Tags:#troubleshooting #mcp #observability #rabbitmq #netdata #incident triage #operator playbook

Ready to run

npx skills add https://github.com/netdata/skills --skill troubleshoot-rabbitmq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: troubleshoot-rabbitmq
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-rabbitmq
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-rabbitmq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Troubleshooting RabbitMQ incidents by turning symptoms like errors, throttling, backpressure, and throughput drops into a structured, signal-driven diagnostic path using Netdata data.

Core Features & Use Cases

MCP-based triage: Queries Netdata via MCP for RabbitMQ health and related host signals instead of relying on guesswork.
Operator playbook routing: Guides an agent through the RabbitMQ operator playbook’s signal domains (availability, resource alarms, throttling & backpressure, throughput, queue depth, resource utilization).
Verification-first remediation: Re-runs the same MCP queries after remediation to confirm the incident resolved and did not merely change the symptom.

Quick Start

Ask an AI agent running Netdata skills: "Diagnose why my RabbitMQ is experiencing errors and throughput degradation and recommend remediation, using Netdata via MCP."

Frequently Asked Questions about troubleshoot-rabbitmq

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

FAQPage Schema

How do I troubleshoot RabbitMQ throughput degradation and backpressure using observability signals?▼

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.

What is the best way to triage RabbitMQ availability incidents during on-call escalation?▼

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.

Why does my RabbitMQ experience throttling and resource alarms, and how can I diagnose it?▼

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.

Can I use Netdata MCP queries to diagnose RabbitMQ errors without manual guesswork?▼

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.

How do I verify RabbitMQ incident remediation and ensure the issue is fully resolved?▼

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.