Databases & queues

RabbitMQ monitoring that reads the queues like an operator.

A queue with no consumers and a climbing depth is tomorrow's outage. The collector reads the management API and turns queue depth, alarms, partitions, and unsynchronised mirrors into ranked issues with the queue named.

What RootTrace watches

Every reading is checked continuously; bad readings become grouped issues with the evidence attached. RootTrace also remembers whether it has seen the same incident before.

Queue depthTotal messages and the specific high queues, by name.
Consumerless queuesQueues receiving messages with nobody consuming them.
ThroughputPublish and deliver rates, so a stalled consumer shows as a widening gap.
Memory & disk alarmsNode alarms with the affected nodes named.
PartitionsNetwork partition count and the partitioned nodes.
Mirror syncMirrored-queue replicas that have fallen out of sync.

Warn and fail thresholds, prefilled

Sensible defaults out of the box, overridable per host with environment variables. No threshold spreadsheet required on day one.

Queue drain-time warn ms ROOTTRACE_RABBITMQ_DRAIN_WARN_MS

Setup

rabbitmq setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_RABBITMQ_API_URL='http://rabbitmq-1:15672'

Read-only by architecture: no write path, no remediation executor, no inbound ports. Credential-like evidence is redacted before it leaves the host.

One collector, live in minutes

Everything on this page comes from the same read-only collector: one command per host, then point it at your targets.

install on any Linux host

$ # after adding the signed RootTrace dnf or apt repository:
sudo dnf install roottrace-collector  # apt: sudo apt install roottrace-collector
sudoedit /etc/roottrace/collector.env  # set ROOTTRACE_COLLECTOR_TOKEN and API URL
sudo roottrace-collector-setup apply
sudo systemctl enable --now roottrace-collector

Questions, answered honestly

Does it need the management plugin?

Yes. The check reads the standard RabbitMQ management API with a read-only user. No AMQP traffic is generated.

Is this safe to run next to production?

The collector is read-only by architecture, not by policy: there is no write path, no remediation executor, and no privileged mode to switch on. It sends short-lived outbound HTTPS requests, opens no inbound ports, and redacts credential-like evidence before anything leaves the host.

Do I need a separate agent for this?

No. One RootTrace collector per host covers every integration on this site: databases, web servers, containers, endpoints, and the Linux host itself, all from one signed package or container. You point it at targets with environment variables; there is nothing else to deploy.

Free on 5 hosts. Live in minutes.

Create a workspace, install one collector, and watch issues explain themselves.

Create free workspace Schedule a demo