SQL Server availability groups
The availability group module watches Always On availability groups on SQL Server 2016 to 2025 (2016 is deprecated): the health and role of every replica, how far each secondary is behind, failovers, the listener and whether backups run where the group says they should.
What it monitors
| Area | Checks | Why it matters |
|---|---|---|
| Replica health | Role, connection and synchronization health of every replica | A disconnected or unhealthy replica can no longer take over |
| Data movement | Send queue, redo queue and estimated data loss per database | Shows how much data a failover would lose and how long recovery would take |
| Failover | Any change of role | Every failover needs an explanation, planned or not |
| Listener | At least one listener IP online | Applications reach the group through it |
| Backups | Backups taken on the preferred replica | Otherwise backup jobs can silently skip |
Every check, with its rule, cause and action, is in the reference for availability group checks.
How Excubius connects
Availability group checks connect through the listener, so they always reach the current primary, which answers for every replica. Instance checks still run against each replica by its own name. The collector uses the same read-only login on every replica; it never needs sysadmin.
In this chapter
ReferencePrerequisitesThe monitoring login, its permissions on every replica and the network.QuickstartAdd an availability groupAdd the replicas, run discovery and see the group on the Overview.TutorialConfigure alertsThresholds from your RPO, Slack routing and a test failover.TroubleshootingTroubleshootingSymptoms, causes and fixes for the most common problems.