Coming soon — in active development
MySQL Monitoring by MonPG
MonPG made one bet for PostgreSQL: incidents end faster when the database evidence — query history, lock chains, replication lag, resource pressure — lives in one workflow. We are now building the same evidence-first monitoring for MySQL and InnoDB. It is not available yet; this page is the honest status.
What we are building
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.
Want to know when it ships?
Drop us a line and we will notify you at launch — early access goes out to this list first.
Request early access →Already running PostgreSQL too? That side is live today — start monitoring PostgreSQL.
MySQL field notes, already publishing
The monitoring product is in development, but the writing is not waiting: we publish practitioner deep dives on InnoDB internals, replication, locking, and MySQL↔PostgreSQL differences.