MySQL Monitoring by MonPG

Live — monitoring MySQL in production

MySQL Monitoring by MonPG

MonPG made one bet: incidents end faster when the database evidence — query history, lock chains, replication lag, resource pressure — lives in one workflow. That same evidence-first monitoring now runs on MySQL and InnoDB. Point the collector at your instance and the dashboards populate in minutes.

What you get

Query digest history

performance_schema statement digests kept over time, so a post-deploy regression is a diff against yesterday’s workload — not a guess.

InnoDB lock and transaction evidence

Lock waits, blocker chains, metadata locks, long transactions, and history list growth in one place when the incident is live.

Replication health

True replica lag, GTID consistency, errant transaction detection, and binlog growth — the signals behind stale reads and failed failovers.

Buffer pool and I/O signals

Buffer pool efficiency, redo pressure, checkpoint stalls, and temp-table spills correlated with the queries that cause them.

Start monitoring MySQL in 5 minutes

Deploy the collector with Docker, Kubernetes, or a standalone binary, point it at your MySQL connection string, and the first query snapshot arrives within a minute. Every plan starts with a free trial.

Start trial →

Running PostgreSQL too? The same collector covers it — see PostgreSQL monitoring.

MySQL field notes

The product ships alongside the writing: we publish practitioner deep dives on InnoDB internals, replication, locking, and MySQL↔PostgreSQL differences.

MySQL topic archive
All field notes