RabbitMQ
See which queues are backing up, whether a memory or disk alarm is blocking publishers, and who is connected and consuming, with a read-only monitoring login.
What it answers
Questions an on-call engineer asks, which an AI client can answer with this plugin.
- Is a memory or disk alarm in effect, and how close is each node to its limits?
- Which queues hold the most messages, and do they have any consumers?
- Which connections are blocked or in flow control, and from which clients?
- Who is consuming from a queue, and with what prefetch and acknowledgement mode?
- Are all shovels running, and why did one stop?
- Which RabbitMQ and Erlang versions run here, and how many messages are queued in total?
What it returns
Each of the plugin's read-only tools, described in words.
- Each RabbitMQ node's resource alarms and usage - memory and disk alarms, memory against its high watermark, free disk against its limit, file descriptors and Erlang processes
- RabbitMQ queues with the most messages first - type, state, ready and unacknowledged messages, consumers, memory, node and publish and delivery rates
- Client connections to RabbitMQ with user, virtual host, protocol, state (running, blocked, flow), channels, client address, TLS and traffic rates
- The RabbitMQ cluster in one row - cluster name, RabbitMQ and Erlang versions, totals of messages, queues, connections, channels and consumers, and message rates
- Consumers on RabbitMQ queues with the queue, consumer tag, user, connection, acknowledgement mode, prefetch count and whether each is active
- RabbitMQ shovels with their state (running, starting, terminated), the node they run on, source and destination queues and why a terminated one stopped
At a glance
- Plugin
- rabbitmq 1.0.0
- Publisher
- levantar
- Platforms
- Linux, Windows, macOS
Tested on
- RabbitMQ 4.4 on macOS (Homebrew), CI runner
- RabbitMQ 4.4.0 on Windows Server (Chocolatey), CI runner
How it logs in
Without an explicit choice, install tries the methods that need no secret first, in this order.
- A user name and password
The least-privilege login
The setup file in the pack. secronyx plugin setup rabbitmq prints it; an administrator applies it by hand.
See it run
Recording coming. Install, setup and status runs for this plugin are recorded on the shared test lab, and appear here once they have run.
Read-only, in layers
Every request is a GET or HEAD to the endpoint the operator configured, on a path fixed in the signed pack. Redirects are not followed, and requests known to change state are refused.
These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.