Coming soon — in active development
SQL Server 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 Microsoft SQL Server, from wait statistics and Query Store to Always On availability groups. It is not available yet; this page is the honest status.
What we are building
Wait statistics history
sys.dm_os_wait_stats snapshots kept over time, so an incident starts from a diff against yesterday's wait profile — not from a since-restart cumulative counter.
Query Store regression evidence
Plan changes, per-plan runtime stats, and forced-plan health surfaced when a deploy makes a query slow — the regression and its old plan in one view.
Blocking and deadlock evidence
Live blocking chains from sys.dm_tran_locks, lead blockers, and captured deadlock graphs from system_health, in one place when the incident is live.
Always On and tempdb signals
Send and redo queue lag per replica, synchronous-commit exposure, plus tempdb allocation contention and version store growth correlated with the sessions causing 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.
SQL Server field notes, already publishing
The monitoring product is in development, but the writing is not waiting: we publish practitioner deep dives on wait statistics, tempdb, Query Store, indexing, isolation levels, and Always On operations.