DumbMonit
IntegraçõesBases de dados e mensagens
Monitorizar RabbitMQ com o DumbMonit
The message broker: memory and disk alarms that block publishers, stopped nodes and partitions, queues filling up with no consumer.
DocumentaçãoSite oficial: RabbitMQ
As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.
O que o DumbMonit vigia
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.
Utilização típica. Message broker: resource alarms, nodes, partitions, queues without consumer
Exemplos
- RabbitMQ single node
- RabbitMQ cluster
Como se liga
O que precisa
- Username / passwordA user tagged monitoring, sent as HTTP basic authentication.
Portas de rede a abrir
15672/TCPManagement API (HTTP, default)15671/TCPOnly if the API is served over TLS (HTTPS, default)
Passos de configuração: 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.
Atenção. A memory or disk alarm blocks every publisher in the cluster, and clients get no error.