SQL Server Monitoring by MonPG

Live — monitoring SQL Server in production

SQL Server 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 Microsoft SQL Server, from wait statistics and Query Store to Always On availability groups. Point the collector at your instance and the dashboards populate in minutes.

What you get

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.

Start monitoring SQL Server in 5 minutes

Deploy the collector with Docker, Kubernetes, or a standalone binary, point it at your SQL Server connection string, and the first 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.

SQL Server field notes

The product ships alongside the writing: we publish practitioner deep dives on wait statistics, tempdb, Query Store, indexing, isolation levels, and Always On operations.

SQL Server topic archive
All field notes