Databases & queues

MongoDB monitoring that names the lagging member.

The collector connects read-only, measures what a DBA would check first, and turns bad readings into grouped issues with evidence: replica lag names the member, saturation shows the percentage, latency shows the milliseconds.

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.

Replica set lagSeconds behind primary, with the lagging member named and initial-sync members counted separately.
Connection saturationCurrent vs. available connections as a percentage, so 'running out' is visible before it happens.
Command & operation latencyRound-trip and operation latency in milliseconds against warn/fail thresholds.
Queued operationsReaders and writers waiting on the storage engine.
OpcountersInsert, query, update, delete, and command rates for context on what changed.
Dependency & reachabilityConnection failures surface as their own issue, not a silent gap.

Warn and fail thresholds, prefilled

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

Replica lag warn / fail seconds ROOTTRACE_MONGODB_WARN_LAG_SECONDS
Connection usage warn / fail percent ROOTTRACE_MONGODB_CONNECTION_WARN_PERCENT
Operation latency warn / fail ms ROOTTRACE_MONGODB_OPERATION_LATENCY_WARN_MS

Setup

mongodb setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_MONGODB_URI='mongodb://user:pass@mongodb-1:27017'

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

How is replica lag measured?

The collector reads replica set status from the instance you point it at, computes each member's lag against the primary, and reports the worst member by name, so the issue says which node to look at, not just that lag exists.

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