Skip to main content

RabbitMQ monitoring with Netdata

RabbitMQ is the open source message broker.

This module monitors RabbitMQ performance and health metrics.

It collects data using following endpoints:

  • /api/overview
  • /api/node/{node_name}
  • /api/vhosts


It produces the following charts:

  • Queued Messages in messages
  • Messages in messages/s
  • Global Counts in counts
  • File Descriptors in descriptors
  • Socket Descriptors in descriptors
  • Erlang Processes in processes
  • Erlang run queue in processes
  • Memory in MiB
  • Disk Space in GiB

Per vhost charts:

  • Messages in messages/s


Edit the go.d/rabbitmq.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/rabbitmq.conf

Here is an example for 2 servers:

- name: local
url: http://localhost:15672
- name: remote

For all available options please see module configuration file.


To troubleshoot issues with the rabbitmq collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m rabbitmq

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.



Last updated on