AI Incident Prevention

AI Incident Center

25 actionable signals across 6 server(s). Highest priority: TESTSRV_3.DBNEXIA.COM / 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-10-14 14:22:04 5 / 5 servers healthy
Critical 25 Needs DBA ownership now
High 0 Likely to repeat or escalate
Next 24h 25 Prevent before next cycle
Servers with risk 6 25 actionable signals
Telemetry gaps 0 Prediction confidence blockers
Incident pressureCritical
Critical
25
High
0
Next 24h
25
Gaps
0
Category driverstop signals
Backup
16
Runtime
5
Concurrency
4
Server health5 / 5 healthy
5 healthy 0 at risk
Response horizonwhen to act
5now
20today
0planned
Evidence sourceswhere signals came from
msdb.dbo.backupset
16
EventLog
5
xml_deadlock_report
4
Server escalation maptop correlated risk
AI war roomresponse capacity
8h
Covered priority-
Remaining effort-
Escalation load49h
Correlation score100 / 100

Top driver is Backup. Correlated server risk is highest when many categories cluster on the same server, so the queue should be handled as incident candidates instead of isolated rows.

Playbook splitfirst moves
16restore readiness
4workload triage
0access/connectivity
0collector repair
AI triage Recommended focus
Next best action 100

TESTSRV_3.DBNEXIA.COM: Open the latest EventLog rows and group by error number, database, host, and SQL text.

Correlated risk 100

TESTSRV_3.DBNEXIA.COM has 8 concurrent signals across Runtime, Backup. Treat it as one incident candidate, not separate noise.

Recovery readiness 84

16 backup risk(s) need attention before they become restore or data-loss exposure.

Concurrency forecast 82

4 blocking/deadlock signal(s) indicate a repeatable access pattern. Fix ordering/indexing before load rises.

Causal analysis Why it happened
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 25 prioritized signals
Risk Server Category Signal ETA Prediction Next DBA action Source
Critical 100 / 100 TESTSRV_3.DBNEXIA.COM - Runtime Event pressure is rising 2,648 signals in 24h. Main driver: errors (2,612). Now 2026-10-14 12:58 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 TESTSRV_5.DBNEXIA.COM - Runtime Event pressure is rising 78 signals in 24h. Main driver: errors (39). Now 2026-10-14 12:58 Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. Start with timeout events: check blocking, waits, recent query changes, and app retry storms. EventLog
Critical 100 / 100 TESTSRV_1.DBNEXIA.COM - Runtime Event pressure is rising 2,746 signals in 24h. Main driver: errors (2,704). Now 2026-10-14 12:58 Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. Review memory grant warnings, spilling queries, and missing indexes before workload queues build up. EventLog
Critical 100 / 100 TESTSRV_2.DBNEXIA.COM - Runtime Event pressure is rising 2,666 signals in 24h. Main driver: errors (2,623). Now 2026-10-14 12:58 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 TESTSRV_4.DBNEXIA.COM - Runtime Event pressure is rising 81 signals in 24h. Main driver: errors (41). Now 2026-10-14 12:58 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 TESTSRV_3.DBNEXIA.COM DOM_MoonCrystal_16FD Backup Backup exposure: DOM_MoonCrystal_16FD FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_2.DBNEXIA.COM DOM_ForestSky_5A7D Backup Backup exposure: DOM_ForestSky_5A7D FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_2.DBNEXIA.COM DOM_WhisperEcho_929E Backup Backup exposure: DOM_WhisperEcho_929E FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_3.DBNEXIA.COM DOM_CrystalStone_911A Backup Backup exposure: DOM_CrystalStone_911A FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_3.DBNEXIA.COM DOM_ShadowMoon_946A Backup Backup exposure: DOM_ShadowMoon_946A FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_3.DBNEXIA.COM DOM_ShadowOcean_4486 Backup Backup exposure: DOM_ShadowOcean_4486 FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_2.DBNEXIA.COM DOM_ForestEcho_B4A4 Backup Backup exposure: DOM_ForestEcho_B4A4 FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_3.DBNEXIA.COM DOM_FlameCrystal_07F4 Backup Backup exposure: DOM_FlameCrystal_07F4 FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_2.DBNEXIA.COM DOM_DreamStone_5722 Backup Backup exposure: DOM_DreamStone_5722 FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_2.DBNEXIA.COM DOM_ShadowRiver_9AF6 Backup Backup exposure: DOM_ShadowRiver_9AF6 FULL. FULL 17d ago, LOG 400h ago <4h 2026-09-27 22:00 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 TESTSRV_3.DBNEXIA.COM dbNexia_db Backup Backup exposure: dbNexia_db SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 TESTSRV_2.DBNEXIA.COM dbNexia_db Backup Backup exposure: dbNexia_db SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 TESTSRV_5.DBNEXIA.COM DBAChaos Backup Backup exposure: DBAChaos SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 TESTSRV_3.DBNEXIA.COM DBAChaos Backup Backup exposure: DBAChaos SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 TESTSRV_5.DBNEXIA.COM dbNexia_db Backup Backup exposure: dbNexia_db SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 TESTSRV_2.DBNEXIA.COM DBAChaos Backup Backup exposure: DBAChaos SIMPLE. FULL 17d ago <4h 2026-09-27 02:00 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 88 / 100 WIN-PN3T1M2LOOO master Concurrency Deadlock detected master / - at 2026-10-14 11:55. <4h 2026-10-14 11:55 Repeated deadlocks usually return after load increases unless the competing access pattern is changed. Open the deadlock graph, identify victim/object/order, then fix index coverage or transaction ordering. xml_deadlock_report
Critical 86 / 100 WIN-PN3T1M2LOOO master Concurrency Deadlock detected master / - at 2026-10-13 17:40. <4h 2026-10-13 17:40 Repeated deadlocks usually return after load increases unless the competing access pattern is changed. Open the deadlock graph, identify victim/object/order, then fix index coverage or transaction ordering. xml_deadlock_report
Critical 86 / 100 WIN-PN3T1M2LOOO master Concurrency Deadlock detected master / - at 2026-10-13 15:55. <4h 2026-10-13 15:55 Repeated deadlocks usually return after load increases unless the competing access pattern is changed. Open the deadlock graph, identify victim/object/order, then fix index coverage or transaction ordering. xml_deadlock_report
Critical 86 / 100 WIN-PN3T1M2LOOO master Concurrency Deadlock detected master / - at 2026-10-13 15:35. <4h 2026-10-13 15:35 Repeated deadlocks usually return after load increases unless the competing access pattern is changed. Open the deadlock graph, identify victim/object/order, then fix index coverage or transaction ordering. xml_deadlock_report