MySQL monitoring that checks the replica threads, not just the lag.

Replication that is 'only a few seconds behind' with a dead SQL thread is still broken. The collector verifies both replica threads, measures lag, and watches the InnoDB lock and connection counters that precede most MySQL incidents.

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.

Replication threads & lagIO and SQL thread status checked independently, plus seconds-behind and replica status errors.
Connection saturationActive vs. max connections, with max-used as the high-water mark.
Aborted & rejected connectionsThe counters that climb when an app or proxy is misconfigured.
InnoDB row locksLock waits and total lock time in milliseconds.
Read-only stateReported so a failover that left a primary read-only is caught immediately.
Connection latencyMilliseconds, against warn/fail thresholds.

Warn and fail thresholds, prefilled

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

Connection usage warn / fail percent ROOTTRACE_MYSQL_CONNECTION_WARN_PERCENT
Replica lag fail seconds ROOTTRACE_MYSQL_REPLICA_LAG_FAIL_SECONDS

Setup

mysql / mariadb setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_MYSQL_DSN='mysql://user:pass@mysql-1:3306/appdb'

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 work with MariaDB?

Yes. The same check speaks to MySQL and MariaDB, including replica status in both dialects.

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