Skip to main content
Version: 0.4 · current

SQL Server checks

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

The sqlserver module has 13 checks. SQL Server on VM / on-prem — instance health, performance and capacity (T-SQL, login with VIEW SERVER STATE).

This page is generated from the product's check catalog when the documentation is built, so the rules, intervals and default severities always match the version you are reading. Thresholds are defaults; entities and resources can override them.

CheckEveryDefault severityRule
sqlserver.cpu_percent
CPU utilization (SQL process)
60swarningwarning > 80 percent · 15m / critical > 90 percent · 5m
sqlserver.ple_seconds
Page life expectancy
60swarningwarning < 1800 seconds · 10m / critical < 600 seconds · 5m
sqlserver.batch_requests
Batch requests per second
60sinfo±2σ over 14d (learning only)
sqlserver.blocked_sessions
Blocked sessions
30swarningwarning >= 1 count · 30s / critical >= 5 count · 60s
sqlserver.deadlocks_per_min
Deadlocks per minute
60swarningwarning > 0 per_minute / critical >= 5 per_minute
sqlserver.top_waits
Top wait categories
60sinfo±2σ over 14d (learning only)
sqlserver.log_space_percent
Transaction log space used
300swarningwarning > 75 percent / critical > 90 percent
sqlserver.backup_age_full
Last full backup age
600swarningwarning > 1560 minutes / critical > 2880 minutes
sqlserver.backup_age_log
Last log backup age
300swarningwarning > 30 minutes / critical > 60 minutes
sqlserver.agent_jobs_failed
SQL Agent job failures (last 24 h)
300swarningwarning >= 1 count / critical >= 3 count
sqlserver.errorlog_severity
Error log entries with severity 16+
120swarningwarning >= 1 count / critical >= 5 count
sqlserver.build_version
Build and update level
3600sinfoany change
sqlserver.linked_server_ping
Linked server reachability and latency
300scriticalwarning > 1000 milliseconds / critical > 5000 milliseconds · 15m

Checks​

sqlserver.cpu_percent

CPU utilization (SQL process)

Measures
cpu_percent (percent) · every 60s · tsql
Rule
warning > 80 percent · 15m / critical > 90 percent · 5m · Default severity: warning
Action
—
Baseline
Sustained CPU above 80% warrants investigation; above 90% for minutes is critical on production. · source

sqlserver.ple_seconds

Page life expectancy

Measures
ple_seconds (seconds) · every 60s · tsql
Rule
warning < 1800 seconds · 10m / critical < 600 seconds · 5m · Default severity: warning
Action
—
Baseline
Rule of thumb: 300 s per 4 GB of buffer pool; defaults assume a 24 GB pool. Adjust per instance.

sqlserver.batch_requests

Batch requests per second

Measures
batch_requests_per_sec (per_second) · every 60s · tsql
Rule
±2σ over 14d (learning only) · Default severity: info
Action
—
Baseline
No fixed threshold; adaptive baseline flags unusual throughput for this instance.

sqlserver.blocked_sessions

Blocked sessions

Measures
blocked_sessions (count) · every 30s · tsql
Rule
warning >= 1 count · 30s / critical >= 5 count · 60s · Default severity: warning
Action
Identify the head blocker (sys.dm_exec_requests / sp_WhoIsActive) before killing anything.
Baseline
Any blocking lasting more than 30 s deserves attention; chains of 5+ sessions are critical.

sqlserver.deadlocks_per_min

Deadlocks per minute

Measures
deadlocks_per_min (per_minute) · every 60s · tsql
Rule
warning > 0 per_minute / critical >= 5 per_minute · Default severity: warning
Action
—
Baseline
Azure Monitor recommended rule for SQL: alert on any deadlock.

sqlserver.top_waits

Top wait categories

Measures
wait_time_ms (milliseconds) · every 60s · tsql
Rule
±2σ over 14d (learning only) · Default severity: info
Action
—
Baseline
Delta-based; the timeline drill-down uses this series.

sqlserver.log_space_percent

Transaction log space used

Measures
log_space_percent (percent) · every 300s · tsql
Rule
warning > 75 percent / critical > 90 percent · Default severity: warning
Action
—
Baseline
Log at 75% means the next growth or a long transaction may fill the volume.

sqlserver.backup_age_full

Last full backup age

Measures
full_age_minutes (minutes) · every 600s · tsql
Rule
warning > 1560 minutes / critical > 2880 minutes · Default severity: warning
Action
—
Baseline
Daily full: warn at 26 h, critical at 48 h. Tie to the entity's RPO policy. A database never backed up counts as infinitely old.

sqlserver.backup_age_log

Last log backup age

Measures
log_age_minutes (minutes) · every 300s · tsql
Rule
warning > 30 minutes / critical > 60 minutes · Default severity: warning
Action
—
Baseline
RPO 15 min → warn at 30, critical at 60.

sqlserver.agent_jobs_failed

SQL Agent job failures (last 24 h)

Measures
failed_jobs (count) · every 300s · tsql
Rule
warning >= 1 count / critical >= 3 count · Default severity: warning
Action
—
Baseline
Any failed job is at least a warning; backup/maintenance jobs can be promoted to critical by tag.

sqlserver.errorlog_severity

Error log entries with severity 16+

Measures
errorlog_entries (count) · every 120s · tsql
Rule
warning >= 1 count / critical >= 5 count · Default severity: warning
Action
—
Baseline
Severity 16+ indicates errors the application must handle; 20+ are fatal. Counts entries of the last 5 minutes.

sqlserver.build_version

Build and update level

Measures
build_info · every 3600s · tsql
Rule
any change · Default severity: info
Action
—
Baseline
Inventory only; the updates module compares it with the latest CU/GDR.

sqlserver.linked_server_ping

Linked server reachability and latency

Measures
latency_ms (milliseconds) · every 300s · tsql
Rule
warning > 1000 milliseconds / critical > 5000 milliseconds · 15m · Default severity: critical
Action
Check network path (VPN tunnel, firewall) first; then the remote service; then provider credentials on the linked server.
Baseline
Warn when a remote round trip exceeds 1 s; 3 consecutive failures or timeouts are critical.