Coming soon — in active development
MariaDB 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 MariaDB, including InnoDB, Aria, and Galera clusters. It is not available yet; this page is the honest status.
What we are building
Query digest history
performance_schema and slow-log digests kept over time, so a post-deploy regression on MariaDB is a diff against yesterday's workload — not a guess.
Storage-engine lock evidence
InnoDB lock waits and blocker chains, Aria and MyISAM table locks, metadata locks, and long transactions in one place when the incident is live.
Galera and replication health
Galera cluster state, flow control, certification conflicts, plus classic replica lag and GTID consistency — the signals behind stalled writes and stale reads.
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.
MariaDB field notes, already publishing
The monitoring product is in development, but the writing is not waiting: we publish practitioner deep dives on InnoDB and Aria internals, Galera clustering, replication, optimizer behavior, and MariaDB↔PostgreSQL differences.