Skip to main content
Version: 0.4 · current

SQL Server availability groups

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansFree · Pro · EnterpriseDeploymentSelf-hosted

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​

AreaChecksWhy it matters
Replica healthRole, connection and synchronization health of every replicaA disconnected or unhealthy replica can no longer take over
Data movementSend queue, redo queue and estimated data loss per databaseShows how much data a failover would lose and how long recovery would take
FailoverAny change of roleEvery failover needs an explanation, planned or not
ListenerAt least one listener IP onlineApplications reach the group through it
BackupsBackups taken on the preferred replicaOtherwise 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​