Overview
RabbitMQ is an open-source message broker that implements the Advanced Message Queuing Protocol (AMQP). Xitoring's RabbitMQ integration provides comprehensive monitoring of queues, exchanges, nodes, and message throughput — helping you ensure reliable message delivery across your applications.
What Can It Monitor?
The RabbitMQ integration organizes metrics into several categories:
Exchanges
- Message rates in/out per exchange
- Exchange type and bindings
Nodes
- CPU and memory usage per node
- File descriptors and socket usage
- Erlang process count
- Disk free space
- Network partitions
Queues
- Queue depth (messages ready / unacknowledged)
- Message rates (publish, deliver, acknowledge)
- Consumer count per queue
- Queue memory usage
Overview
- Total connections and channels
- Global message rates
- Cluster-wide publish/deliver rates
Octets
- Network bytes sent and received
Prerequisites
Enable the Management Plugin
The RabbitMQ management plugin must be enabled before Xitoring can collect metrics:
rabbitmq-plugins enable rabbitmq_management
No node restart is required after enabling the plugin. The management API will be available at http://127.0.0.1:15672 by default.
How to Activate the Integration
Run the Xitogent CLI:
xitogent integrate
Select RabbitMQ from the list. When prompted, provide:
- URL (e.g.,
http://127.0.0.1:15672) - Username (default:
guest) - Password (default:
guest)
Xitogent tests the connection and sets up the rest automatically. Within a minute, graphs and data appear on your server page.
Setting Up Triggers
Available trigger categories:
- Exchanges — Message rate thresholds per exchange
- Nodes — CPU, memory, disk, file descriptor alerts
- Queues — Queue depth, consumer count, message rate alerts
- Overview — Connection count, global message rates
- Octets — Network throughput thresholds
Navigate to Triggers on your server page, select RabbitMQ, choose the category and metric, set your threshold, and configure notifications.
Tips
- Always enable the management plugin — it's required for metric collection
- Monitor Queue Depth closely — growing queues indicate consumers can't keep up
- Set alerts on Node Memory to prevent out-of-memory crashes
- Track Consumer Count per queue to detect disconnected consumers
- Watch for Network Partitions in clustered setups — they can cause split-brain scenarios
- Works on both Linux and Windows servers