LavinMQ monitoring and observability

Disk first, then everything else

LavinMQ is built to be lean: it writes messages to disk and keeps memory use low. That shifts what you watch. Free disk space is the limit that matters most, followed by queues that grow, consumers that fall behind and connections that come and go. Monitoring shows you the signs before they turn into an outage, and when something does break, the right metrics and logs point you to the cause instead of leaving you to guess.

Where LavinMQ metrics come from

LavinMQ has everything you need built in. No plugins to enable.

• Prometheus endpoint. Aggregated metrics on /metrics, port 15692, bound to 127.0.0.1 by default. Point your scraper there.
• Detailed metrics. Per-queue, per-connection and per-channel series on /metrics/detailed. Ask for specific families and vhosts to keep the number of series down.
• Management interface and API. Statistics every five seconds, with about ten minutes of history.
• Logs. Stream them live from the API, download recent logs, or route them to the internal amq.lavinmq.log exchange with severity as the routing key.

What to watch in LavinMQ

Start with these. Each card lists the metrics to look for on the Prometheus endpoint.

See every metric in the LavinMQ monitoring docs

Tips from the LavinMQ docs

• Alert on queue depth, unacked growth, dead-letter growth, memory and file descriptor headroom, low disk space and follower lag.
• Query the replication counters with rate() or increase(), since they reset when a follower reconnects.
• Watch socket_buffer_pool_dropped_total. Steady growth means more busy connections at once than the buffer cache can hold.

Learn more