Skip to content
RabbitMQ Monitoring for Zenoss
Python JavaScript
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.




This project is a Zenoss extension (ZenPack) that allows for monitoring of RabbitMQ. See the Usage section for details on what is monitored. You can watch the Monitoring RabbitMQ video for a quick introduction that covers most of the details below.


Prerequisite Restriction
Zenoss Platform 3.2 or greater
Zenoss Processes zenmodeler, zencommand
Installed ZenPacks ZenPacks.zenoss.RabbitMQ
Firewall Acccess Collector server to 2/tcp of RabbitMQ server

Related ZenPacks

There already exist at least two community Zenpacks that provide monitoring for RabbitMQ.

  • ZenPacks.dnalley.AMQPEventMonitor by David Nalley: Very different functionality than what's provided by this ZenPack. It allows you to pull messages from a defined queue and automatically turn them into Zenoss events.
  • by Greg Guthe: More similar to this ZenPack in its functionality. Global metrics for queued messages and rates. It appears to require that the HTTP management API plugin be installed into your RabbitMQ instances, and that a Net-SNMP extension also written by Greg Guthe be installed.

The major differences between the and this pack are that this pack simply runs various rabbitmqctl commands over SSH both to model the node, vhosts, exchanges and queues; as well as to monitor connection, channel and per-queue metrics. So you don't need to install anything extra on your RabbitMQ server, and you get more granularity on the monitoring.

In the future this pack might be extended to also support RabbitMQ's HTTP management API plugin in addition to the SSH method.



This ZenPack has no special installation considerations. You should install the most recent version of the ZenPack for the version of Zenoss you're running.

The ZenPack can be downloaded from

To install the ZenPack you must copy the .egg file to your Zenoss master server and run the following command as the zenoss user:

zenpack --install <filename.egg>

After installing you must restart Zenoss by running the following command as the zenoss user on your master Zenoss server:

zenoss restart

If you have distributed collectors you must also update them after installing the ZenPack.


Installing the ZenPack will add the following objects to your Zenoss system.

  • Modeling Plugins
    • zenoss.ssh.RabbitMQ
  • Monitoring Templates
    • RabbitMQNode in /Devices
    • RabbitMQQueue in /Devices
  • Event Classes
    • /Status/RabbitMQ
    • /Perf/RabbitMQ
  • Command Parsers
    • ZenPacks.zenoss.RabbitMQ.parsers.RabbitMQCTL

These monitoring templates should not be bound directly to any devices in the system.

To start monitoring your RabbitMQ server you will need to setup SSH access so that your Zenoss collector server will be able to SSH into your RabbitMQ server(s) as a user who has permission to run the rabbitmqctl command. This almost always means the root user. See the Using a Non-Root User section below for instructions on allowing non-root users to run rabbitmqctl. To do this you need to set the following zProperties for the RabbitMQ devices or their device class in Zenoss.

  • zCommandUsername
  • zCommandPassword
  • zKeyPath

The zCommandUsername property must be set. To use public key authentication you must verify that the public portion of the key referenced in zKeyPath is installed in the ~/.ssh/authorized_keys file for the appropriate user on the RabbitMQ server. If this key has a passphrase you should set it in the zCommandPassword property. If you'd rather use password authentication than setup keys, simply put the user's password in the zCommandPassword property.

You should then add the zenoss.ssh.RabbitMQ modeler plugin to the device, or device class containing your RabbitMQ servers and remodel the device(s). This will automatically find the node, vhosts, exchanges and queues and begin monitoring them immediately for the following metrics.

  • Node Values
    • Status - Running or not? Generates event on failure.
    • Open Connections & Channels
    • Sent & Received Bytes Rate
    • Sent & Received Messages Rate
    • Depth of Send Queue
    • Consumers
    • Unacknowledged & Uncommitted Messages
  • Queue Values
    • Ready, Unacknowledged & Total Messages
    • Memory Usage
    • Consumers

There is a default threshold of 1,000,000 messages per queue. This is almost certainly an absurdly high threshold that shouldn't trip in normal systems. However, by clicking into the details of any individual queue you can set the per-queue threshold to a more reasonable value that makes sense for a given queue.

Using a Non-Root User

This ZenPack requires the ability to run the rabbitmqctl command remotely on your RabbitMQ server(s) using SSH. By default, the rabbitmqctl command is only allowed to be run by the root and rabbitmq users. Furthermore, this ZenPack expects the rabbitmqctl command be in the user's path. Normally this is only true for the root user.


There's a very good reason for this restriction. Once a user is allowed to execute the rabbitmqctl command, they are able to perform the following actions.

  • Stop, Start or Reset RabbitMQ
  • Control a RabbitMQ Cluster
  • Close Open Connections
  • Manage Users and Security
  • Manage VHosts

In a nutshell, this means that any user with permission to run rabbitmqctl can wreak total havoc on your RabbitMQ server if they had the intent to do so.

Assuming that you've created a user named zenoss on your RabbitMQ servers for monitoring purposes, you can follow these steps to allow the zenoss user to run rabbitmqctl.

  1. Copy RabbitMQ's Erlang cookie to the zenoss user's home directory:

    .. sourcecode:: bash

    su - cp /var/lib/rabbitmq/.erlang-cookie /home/zenoss chown zenoss:zenoss /home/zenoss/.erlang-cookie chmod 0400 /home/zenoss/.erlang-cookie

  2. Add /usr/sbin to the zenoss user's path.

    echo 'export PATH="$PATH:/usr/sbin"' >> /home/zenoss/.bashrc


  • Components


  • Nodes


  • Node Throughput

    Node Throughput

  • Node Channels

    Node Channels

  • VHosts


  • Queues


  • Queue Metrics

    Queue Metrics

Something went wrong with that request. Please try again.