DumbMonit
EN
GitHub Install

IntegrationsDatabases and messaging

Monitor RabbitMQ with DumbMonit

The message broker: memory and disk alarms that block publishers, stopped nodes and partitions, queues filling up with no consumer.

DocumentationOfficial website: RabbitMQ

Product descriptions are in English, as in the product. The page labels follow your language.

What DumbMonit watches

The message broker: memory and disk alarms, stopped nodes and network partitions, queues that fill up with nobody reading them, queues that are no longer running, and the flow of messages.

Typical use. Message broker: resource alarms, nodes, partitions, queues without consumer

Examples

  • RabbitMQ single node
  • RabbitMQ cluster

How it connects

What you need

  • Username / passwordA user tagged monitoring, sent as HTTP basic authentication.

Network ports to open

  • 15672/TCPManagement API (HTTP, default)
  • 15671/TCPOnly if the API is served over TLS (HTTPS, default)
Setup steps: Create a RabbitMQ monitoring user

  1. Open the RabbitMQ management interface, for example http://rabbit.lan:15672, and log in with a user allowed to manage users.

  2. Go to Admin → Users → Add a user, name it dumbmonit, set a password and the tag monitoring, then click Add user.

  3. Click dumbmonit in the list, and under Set permission pick each virtual host, set Configure, Write and Read to ^$, then click Set permission.

  4. In DumbMonit, enter the address of one node, for example rabbit.lan, or https://rabbit.lan:15671 when the API is served over TLS.

Heads-up. A memory or disk alarm blocks every publisher in the cluster, and clients get no error.

Also in Databases and messaging