Connections & Observability
The RabbitMQ (AMQP 0-9-1) connector's observability surface — the connections and topology endpoints, Prometheus metrics, the SSE feed, and audit events.
This reference documents the RabbitMQ (AMQP 0-9-1) connector's observability surface: the
dashboard HTTP endpoints, the Prometheus metric families, the SSE feed, and the
audit events the connector emits. The dashboard APIs are on the internal API port and
are network-protected like all /api/* routes.
Dashboard APIs
GET /api/amqp/connections
Node-local live connection list with per-connection metadata: client ID, source IP, channels, consumers, and vhost. Use it to confirm the connector accepted connections after an upgrade — see Configuration.
GET /api/amqp/topology
Cluster-synced view of exchanges, queues, and bindings, with message and consumer counts and
inert-argument badges (x-max-length-bytes, x-queue-type, x-queue-mode and
x-max-priority are flagged here so operators can see that a queue declared with one of them
is not actually enforcing it — enforced arguments such as x-max-length are not badged). See
Capabilities.
Prometheus metrics
Gauges
| Metric | Meaning |
|---|---|
kubemq_amqp_connections | Live AMQP connections |
kubemq_amqp_channels | Live AMQP channels |
kubemq_amqp_consumers | Live AMQP consumers |
Counters
| Metric | Meaning |
|---|---|
kubemq_amqp_publishes_total{vhost} | Publishes, by vhost |
kubemq_amqp_delivers_total{vhost} | Deliveries, by vhost |
kubemq_amqp_confirms_nacked_total | Publisher-confirm nacks (gotcha #3) |
kubemq_amqp_returns_total | basic.return events (mandatory unroutable, 312) |
SSE feed
The connectors SSE event carries an "amqp" group key with per-vhost stats:
{
"connections": 3,
"channels": 7,
"consumers": 5,
"publishes_total": 1024,
"delivers_total": 1019,
"confirms_nacked_total": 0,
"returns_total": 2,
"vhosts": { "default": { "publishes_total": 1024, "delivers_total": 1019 } }
}Audit events
Audit events use Transport amqp and carry SourceIP and ClientID:
| Event | When |
|---|---|
client.connected / client.disconnected / client.timeout | Connection lifecycle |
auth.success / auth.failure | SASL PLAIN authentication outcome |
amqp.exchange.declared / amqp.exchange.deleted | Exchange lifecycle |
amqp.queue.declared / amqp.queue.deleted | Queue lifecycle |
amqp.binding.created / amqp.binding.deleted | Binding lifecycle |
subscription.created / subscription.deleted | Consumer lifecycle |
amqp.publish.denied | Write denial on the exchange at publish time (the channel is closed 403) |
amqp.dlx.routed | A message was dead-lettered |
Related
Capabilities
The forced caps and inert-argument badges that this endpoint surfaces.
Error & Reason Codes
The 311–541 close codes behind confirms_nacked_total and returns_total.
Authentication
The SASL PLAIN / AMQPLAIN / EXTERNAL outcomes behind auth.success / auth.failure and amqp.publish.denied.
Reliability
Publisher confirms, returns, and dead-lettering as observed through these metrics.
Was this page helpful?
Configuration reference
Every Connectors.Amqp.* field of the KubeMQ RabbitMQ connector — CONNECTORS_AMQP_* variables, credentials, certificate login, management listener, validation.
Error & Reason Codes
The AMQP 0-9-1 channel and connection close codes (311–541) the KubeMQ RabbitMQ connector returns — their meanings, triggers, and channel-vs-connection scope.