DumbMonit
IntégrationsBases de données et messagerie
Surveiller RabbitMQ avec DumbMonit
The message broker: memory and disk alarms that block publishers, stopped nodes and partitions, queues filling up with no consumer.
DocumentationSite officiel : RabbitMQ
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
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.
Usage typique. Message broker: resource alarms, nodes, partitions, queues without consumer
Exemples
- RabbitMQ single node
- RabbitMQ cluster
Comment il se connecte
Ce qu'il faut
- Username / passwordA user tagged monitoring, sent as HTTP basic authentication.
Ports réseau à ouvrir
15672/TCPManagement API (HTTP, default)15671/TCPOnly if the API is served over TLS (HTTPS, default)
Étapes de mise en place: Create a RabbitMQ monitoring user
Open the RabbitMQ management interface, for example http://rabbit.lan:15672, and log in with a user allowed to manage users.
Go to Admin → Users → Add a user, name it dumbmonit, set a password and the tag monitoring, then click Add user.
Click dumbmonit in the list, and under Set permission pick each virtual host, set Configure, Write and Read to ^$, then click Set permission.
In DumbMonit, enter the address of one node, for example rabbit.lan, or https://rabbit.lan:15671 when the API is served over TLS.
À savoir. A memory or disk alarm blocks every publisher in the cluster, and clients get no error.