Response horizonwhen to act
3now
38today
0planned
AI Incident Prevention
AI Incident Center
41 actionable signals across 5 server(s). Highest priority: SERVER 2 / Event pressure is rising. Runtime failures, backup exposure, security anomalies, blocking, deadlocks and telemetry gaps are prioritized here. Capacity forecasting is handled separately under Forecast.
Critical
2026-06-21 05:25:46
5 / 5 servers healthy
Critical
26
Needs DBA ownership now
High
0
Likely to repeat or escalate
Next 24h
41
Prevent before next cycle
Servers with risk
5
41 actionable signals
Telemetry gaps
0
Prediction confidence blockers
Incident pressureCritical
Category driverstop signals
Server health5 / 5 healthy
5 healthy
0 at risk
Evidence sourceswhere signals came from
Server escalation maptop correlated risk
AI triage
Recommended focus
Next best action
100
SERVER 2: Open the latest EventLog rows and group by error number, database, host, and SQL text.
Correlated risk
100
SERVER 2 has 11 concurrent signals across Runtime, Backup, Security. Treat it as one incident candidate, not separate noise.
Recovery readiness
84
23 backup risk(s) need attention before they become restore or data-loss exposure.
Server focus
Correlated incident candidates
Selected signal
Click an incident row
Select an incident signal to see prediction, evidence and the DBA action plan.
Incident queue
41 prioritized signals
| Risk | Server | Category | Signal | ETA | Prediction | Next DBA action | Source |
|---|---|---|---|---|---|---|---|
| Critical 100 / 100 | SERVER 2 - | Runtime | Event pressure is rising 885 signals in 24h. Main driver: errors (885). | Now 2026-06-20 21:30 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Open the latest EventLog rows and group by error number, database, host, and SQL text. | EventLog |
| Critical 100 / 100 | SERVER 1 - | Runtime | Event pressure is rising 1,022 signals in 24h. Main driver: errors (1,022). | Now 2026-06-20 21:30 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Open the latest EventLog rows and group by error number, database, host, and SQL text. | EventLog |
| Critical 100 / 100 | SERVER 3 - | Runtime | Event pressure is rising 879 signals in 24h. Main driver: errors (879). | Now 2026-06-20 21:30 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Open the latest EventLog rows and group by error number, database, host, and SQL text. | EventLog |
| Critical 100 / 100 | SERVER 1 MAL_MAINT_DB | Backup | Backup exposure: MAL_MAINT_DB SIMPLE. FULL 442d ago | <4h 2025-04-04 12:38 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 MAL_MAINT_DB | Backup | Backup exposure: MAL_MAINT_DB SIMPLE. FULL 442d ago | <4h 2025-04-04 12:38 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 MAL_MAINT_DB | Backup | Backup exposure: MAL_MAINT_DB SIMPLE. FULL 442d ago | <4h 2025-04-04 12:38 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 DOM_BlossomWhisper_FDD3 | Backup | Backup exposure: DOM_BlossomWhisper_FDD3 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 DOM_DreamBlossom_D66E | Backup | Backup exposure: DOM_DreamBlossom_D66E FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 DOM_ForestDream_BD6D | Backup | Backup exposure: DOM_ForestDream_BD6D FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 DOM_ShadowWhisper_67B1 | Backup | Backup exposure: DOM_ShadowWhisper_67B1 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 DOM_ThunderMoon_622B | Backup | Backup exposure: DOM_ThunderMoon_622B FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 DOM_DreamStone_5722 | Backup | Backup exposure: DOM_DreamStone_5722 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 DOM_ForestEcho_B4A4 | Backup | Backup exposure: DOM_ForestEcho_B4A4 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 DOM_ForestSky_5A7D | Backup | Backup exposure: DOM_ForestSky_5A7D FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 DOM_ShadowRiver_9AF6 | Backup | Backup exposure: DOM_ShadowRiver_9AF6 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 DOM_WhisperEcho_929E | Backup | Backup exposure: DOM_WhisperEcho_929E FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 DOM_CrystalStone_911A | Backup | Backup exposure: DOM_CrystalStone_911A FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 DOM_FlameCrystal_07F4 | Backup | Backup exposure: DOM_FlameCrystal_07F4 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 DOM_MoonCrystal_16FD | Backup | Backup exposure: DOM_MoonCrystal_16FD FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 DOM_ShadowMoon_946A | Backup | Backup exposure: DOM_ShadowMoon_946A FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 DOM_ShadowOcean_4486 | Backup | Backup exposure: DOM_ShadowOcean_4486 FULL. FULL missing, LOG missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run or repair log backups, validate the log backup job, and confirm the database recovery model is intentional. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 1 MAL_MAINT_DB_old | Backup | Backup exposure: MAL_MAINT_DB_old SIMPLE. FULL missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 2 MAL_MAINT_DB_old | Backup | Backup exposure: MAL_MAINT_DB_old SIMPLE. FULL missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 3 MAL_MAINT_DB_old | Backup | Backup exposure: MAL_MAINT_DB_old SIMPLE. FULL missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 4 MAL_MAINT_DB | Backup | Backup exposure: MAL_MAINT_DB SIMPLE. FULL missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Critical 100 / 100 | SERVER 5 MAL_MAINT_DB | Backup | Backup exposure: MAL_MAINT_DB SIMPLE. FULL missing | <4h latest sample | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Run a verified full backup and confirm the job schedule, retention, and destination health. | msdb.dbo.backupset |
| Warning 68 / 100 | SERVER 4 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-19 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 4 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-19 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 4 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-19 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 1 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-18 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 3 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-18 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 2 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-18 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 3 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 3 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 2 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 2 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 5 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 5 - | Security | Login failure pattern LGIF: Login failed. The login is from an untrusted domain and cannot be used with Integrated authenticatio Login failed. The login is from an untrusted domain and cannot be used with Integrated authenticatio | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 5 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-17 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 1 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-15 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |
| Warning 68 / 100 | SERVER 1 - | Security | Login failure pattern LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th | <24h 2026-06-11 04:05 | Repeated login failures can indicate broken applications, expired credentials, or unwanted access attempts. | Group by login/host/app, separate expected service-account failures from suspicious activity, and fix the source. | AuditLog |