DumbMonit
IntegracionesBases de datos y mensajería
Monitorizar RabbitMQ con DumbMonit
The message broker: memory and disk alarms that block publishers, stopped nodes and partitions, queues filling up with no consumer.
DocumentaciónSitio web oficial: RabbitMQ
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
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.
Uso habitual. Message broker: resource alarms, nodes, partitions, queues without consumer
Ejemplos
- RabbitMQ single node
- RabbitMQ cluster
Cómo se conecta
Qué necesita
- Username / passwordA user tagged monitoring, sent as HTTP basic authentication.
Puertos de red que abrir
15672/TCPManagement API (HTTP, default)15671/TCPOnly if the API is served over TLS (HTTPS, default)
Pasos de configuración: 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.
Ojo. A memory or disk alarm blocks every publisher in the cluster, and clients get no error.