MariaDB Monitoring by MonPG
Live — monitoring MariaDB in production
MariaDB 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 MariaDB, including InnoDB, Aria, and Galera clusters. Point the collector at your instance and the dashboards populate in minutes.
What you get
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.
Start monitoring MariaDB in 5 minutes
Deploy the collector with Docker, Kubernetes, or a standalone binary, point it at your MariaDB connection string, and the first query snapshot arrives within a minute. Every plan starts with a free trial.
Running PostgreSQL too? The same collector covers it — see PostgreSQL monitoring.
MariaDB field notes
The product ships alongside the writing: we publish practitioner deep dives on InnoDB and Aria internals, Galera clustering, replication, optimizer behavior, and MariaDB↔PostgreSQL differences.