Comprobaciones de SQL Server
El módulo sqlserver tiene 13 comprobaciones. SQL Server en máquinas virtuales o en el entorno local: salud, rendimiento y capacidad de la instancia (T-SQL, inicio de sesión con VIEW SERVER STATE).
Esta página se genera a partir del catálogo de comprobaciones del producto al compilar la documentación, así que las reglas, los intervalos y las severidades predeterminadas siempre coinciden con la versión que estás leyendo. Los umbrales son valores predeterminados; las entidades y los recursos pueden reemplazarlos.
| Comprobación | Cada | Severidad predeterminada | Regla |
|---|---|---|---|
sqlserver.cpu_percentCPU utilization (SQL process) | 60s | warning | warning > 80 percent · 15m / critical > 90 percent · 5m |
sqlserver.ple_secondsPage life expectancy | 60s | warning | warning < 1800 seconds · 10m / critical < 600 seconds · 5m |
sqlserver.batch_requestsBatch requests per second | 60s | info | ±2σ over 14d (learning only) |
sqlserver.blocked_sessionsBlocked sessions | 30s | warning | warning >= 1 count · 30s / critical >= 5 count · 60s |
sqlserver.deadlocks_per_minDeadlocks per minute | 60s | warning | warning > 0 per_minute / critical >= 5 per_minute |
sqlserver.top_waitsTop wait categories | 60s | info | ±2σ over 14d (learning only) |
sqlserver.log_space_percentTransaction log space used | 300s | warning | warning > 75 percent / critical > 90 percent |
sqlserver.backup_age_fullLast full backup age | 600s | warning | warning > 1560 minutes / critical > 2880 minutes |
sqlserver.backup_age_logLast log backup age | 300s | warning | warning > 30 minutes / critical > 60 minutes |
sqlserver.agent_jobs_failedSQL Agent job failures (last 24 h) | 300s | warning | warning >= 1 count / critical >= 3 count |
sqlserver.errorlog_severityError log entries with severity 16+ | 120s | warning | warning >= 1 count / critical >= 5 count |
sqlserver.build_versionBuild and update level | 3600s | info | any change |
sqlserver.linked_server_pingLinked server reachability and latency | 300s | critical | warning > 1000 milliseconds / critical > 5000 milliseconds · 15m |
Comprobaciones
sqlserver.cpu_percent
CPU utilization (SQL process)
- Mide
cpu_percent(percent) · cada60s·tsql- Regla
warning > 80 percent · 15m / critical > 90 percent · 5m· Severidad predeterminada: warning- Acción
- —
- Línea base
- Sustained CPU above 80% warrants investigation; above 90% for minutes is critical on production. · origen
sqlserver.ple_seconds
Page life expectancy
- Mide
ple_seconds(seconds) · cada60s·tsql- Regla
warning < 1800 seconds · 10m / critical < 600 seconds · 5m· Severidad predeterminada: warning- Acción
- —
- Línea base
- 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
- Mide
batch_requests_per_sec(per_second) · cada60s·tsql- Regla
±2σ over 14d (learning only)· Severidad predeterminada: info- Acción
- —
- Línea base
- No fixed threshold; adaptive baseline flags unusual throughput for this instance.
sqlserver.blocked_sessions
Blocked sessions
- Mide
blocked_sessions(count) · cada30s·tsql- Regla
warning >= 1 count · 30s / critical >= 5 count · 60s· Severidad predeterminada: warning- Acción
- Identify the head blocker (sys.dm_exec_requests / sp_WhoIsActive) before killing anything.
- Línea base
- Any blocking lasting more than 30 s deserves attention; chains of 5+ sessions are critical.
sqlserver.deadlocks_per_min
Deadlocks per minute
- Mide
deadlocks_per_min(per_minute) · cada60s·tsql- Regla
warning > 0 per_minute / critical >= 5 per_minute· Severidad predeterminada: warning- Acción
- —
- Línea base
- Azure Monitor recommended rule for SQL: alert on any deadlock.
sqlserver.top_waits
Top wait categories
- Mide
wait_time_ms(milliseconds) · cada60s·tsql- Regla
±2σ over 14d (learning only)· Severidad predeterminada: info- Acción
- —
- Línea base
- Delta-based; the timeline drill-down uses this series.
sqlserver.log_space_percent
Transaction log space used
- Mide
log_space_percent(percent) · cada300s·tsql- Regla
warning > 75 percent / critical > 90 percent· Severidad predeterminada: warning- Acción
- —
- Línea base
- Log at 75% means the next growth or a long transaction may fill the volume.
sqlserver.backup_age_full
Last full backup age
- Mide
full_age_minutes(minutes) · cada600s·tsql- Regla
warning > 1560 minutes / critical > 2880 minutes· Severidad predeterminada: warning- Acción
- —
- Línea base
- 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
- Mide
log_age_minutes(minutes) · cada300s·tsql- Regla
warning > 30 minutes / critical > 60 minutes· Severidad predeterminada: warning- Acción
- —
- Línea base
- RPO 15 min → warn at 30, critical at 60.
sqlserver.agent_jobs_failed
SQL Agent job failures (last 24 h)
- Mide
failed_jobs(count) · cada300s·tsql- Regla
warning >= 1 count / critical >= 3 count· Severidad predeterminada: warning- Acción
- —
- Línea base
- 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+
- Mide
errorlog_entries(count) · cada120s·tsql- Regla
warning >= 1 count / critical >= 5 count· Severidad predeterminada: warning- Acción
- —
- Línea base
- 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
- Mide
build_info· cada3600s·tsql- Regla
any change· Severidad predeterminada: info- Acción
- —
- Línea base
- Inventory only; the updates module compares it with the latest CU/GDR.
sqlserver.linked_server_ping
Linked server reachability and latency
- Mide
latency_ms(milliseconds) · cada300s·tsql- Regla
warning > 1000 milliseconds / critical > 5000 milliseconds · 15m· Severidad predeterminada: critical- Acción
- Check network path (VPN tunnel, firewall) first; then the remote service; then provider credentials on the linked server.
- Línea base
- Warn when a remote round trip exceeds 1 s; 3 consecutive failures or timeouts are critical.
Contenido relacionado
- SQL Server: requisitos previos y cómo agregar recursos
- Umbrales y líneas base: cómo se reemplaza un umbral predeterminado