Monitoring & incidents · wired today

RabbitMQ, wired into your agent workforce

Incidents move faster than humans can tab-switch. The RabbitMQ connector is one of 205 executable connectors and gives agents 7 read-only tools, with the credential held in the vault and every call receipted.

Connecting RabbitMQ takes one credential

You provide base URL, username, password from your RabbitMQ account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: RabbitMQ's own API documentation ↗ covers creating and scoping the credential.

What agents can run against RabbitMQ

overview

Get the broker overview: RabbitMQ and Erlang versions, cluster name, total object and message counts, and the global message rates

list_nodes

List the cluster nodes with their running state, memory and disk alarms, and file-descriptor and socket usage

list_vhosts

List the virtual hosts with their message counts and message rates

list_queues

List queues with their vhost, node, durability, consumer count and ready/unacknowledged message depth

list_exchanges

List exchanges with their vhost, type (direct/fanout/topic/headers), durability and internal flag

list_connections

List client connections with their peer host, protocol, authenticated user, vhost, channel count and connection state

healthchecks_alarms

Check whether any resource alarm (memory or disk) is in effect across the cluster; returns ok or a failure reason

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running RabbitMQ instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.

RabbitMQ integration FAQ

What can Quox agents do with RabbitMQ?

Agents can run 7 read-only tools against RabbitMQ: overview, list nodes, list vhosts, list queues, list exchanges and more. Every call is receipted in the evidence trail.

What does the RabbitMQ integration need?

You provide base URL, username, password from your RabbitMQ account; Quox sends it as HTTP basic credentials. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my RabbitMQ credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the RabbitMQ connector?