Response horizonwhen to act
5now
124today
0planned
Incident Prevention
AI Incidents
129 actionable signals across 5 server(s). Highest priority: TESTSRV_1.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-08-07 07:07:03
5 / 5 servers healthy
Critical
55
Needs DBA ownership now
High
48
Likely to repeat or escalate
Next 24h
129
Prevent before next cycle
Servers with risk
5
129 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 war roomresponse capacity
8h
Covered priority-
Remaining effort-
Escalation load207h
Correlation score100 / 100
Top driver is Security. 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
25restore readiness
39workload triage
60access/connectivity
0collector repair
AI triage
Recommended focus
Next best action
100
TESTSRV_1.DBNEXIA.COM: Review memory grant warnings, spilling queries, and missing indexes before workload queues build up.
Correlated risk
100
TESTSRV_1.DBNEXIA.COM has 27 concurrent signals across Runtime, Backup, Concurrency, Security. Treat it as one incident candidate, not separate noise.
Recovery readiness
84
25 backup risk(s) need attention before they become restore or data-loss exposure.
Concurrency forecast
82
36 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
129 prioritized signals
| Risk | Server | Category | Signal | ETA | Prediction | Next DBA action | Source |
|---|---|---|---|---|---|---|---|
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM - | Runtime | Event pressure is rising 3,312 signals in 24h. Main driver: errors (2,899). | Now 2026-08-07 07:00 | 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 3,201 signals in 24h. Main driver: errors (2,787). | Now 2026-08-07 06:00 | 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_3.DBNEXIA.COM - | Runtime | Event pressure is rising 3,164 signals in 24h. Main driver: errors (2,721). | Now 2026-08-07 05:29 | 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_5.DBNEXIA.COM - | Runtime | Event pressure is rising 239 signals in 24h. Main driver: timeouts (122). | Now 2026-08-07 05:29 | 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_4.DBNEXIA.COM - | Runtime | Event pressure is rising 234 signals in 24h. Main driver: timeouts (119). | Now 2026-08-07 05:10 | 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 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 | TESTSRV_1.DBNEXIA.COM 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 | TESTSRV_1.DBNEXIA.COM 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 | TESTSRV_1.DBNEXIA.COM 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 | TESTSRV_1.DBNEXIA.COM 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 | TESTSRV_2.DBNEXIA.COM 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 | TESTSRV_2.DBNEXIA.COM 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 | TESTSRV_2.DBNEXIA.COM 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 | TESTSRV_2.DBNEXIA.COM 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 | TESTSRV_2.DBNEXIA.COM 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 | TESTSRV_3.DBNEXIA.COM 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 | TESTSRV_3.DBNEXIA.COM 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 | TESTSRV_3.DBNEXIA.COM 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 | TESTSRV_3.DBNEXIA.COM 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 | TESTSRV_3.DBNEXIA.COM 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 | TESTSRV_1.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos 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 | TESTSRV_1.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_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 | TESTSRV_2.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos 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 | TESTSRV_2.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_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 | TESTSRV_3.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos 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 | TESTSRV_3.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_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 | TESTSRV_4.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos 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 | TESTSRV_4.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_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 | TESTSRV_5.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos 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 | TESTSRV_5.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_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 90 / 100 | TESTSRV_1.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 07:00. | <4h 2026-08-07 07:00 | 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 90 / 100 | TESTSRV_1.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-08-07 07:00. | <4h 2026-08-07 07:00 | 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 90 / 100 | TESTSRV_1.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 07:00. | <4h 2026-08-07 07:00 | 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 90 / 100 | TESTSRV_2.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 06:00. | <4h 2026-08-07 06:00 | 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 90 / 100 | TESTSRV_2.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-08-07 06:00. | <4h 2026-08-07 06:00 | 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 90 / 100 | TESTSRV_2.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 06:00. | <4h 2026-08-07 06:00 | 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 88 / 100 | TESTSRV_2.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-08-07 05:00. | <4h 2026-08-07 05:00 | 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 88 / 100 | TESTSRV_2.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 05:00. | <4h 2026-08-07 05:00 | 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 88 / 100 | TESTSRV_5.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-08-07 05:00. | <4h 2026-08-07 05:00 | 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 88 / 100 | TESTSRV_5.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 05:00. | <4h 2026-08-07 05:00 | 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 88 / 100 | TESTSRV_5.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 05:00. | <4h 2026-08-07 05:00 | 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 88 / 100 | TESTSRV_5.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 04:00. | <4h 2026-08-07 04:00 | 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 88 / 100 | TESTSRV_5.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 04:00. | <4h 2026-08-07 04:00 | 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 88 / 100 | TESTSRV_3.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 04:00. | <4h 2026-08-07 04:00 | 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 88 / 100 | TESTSRV_3.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 04:00. | <4h 2026-08-07 04:00 | 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 88 / 100 | TESTSRV_3.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 03:00. | <4h 2026-08-07 03:00 | 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 88 / 100 | TESTSRV_3.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 03:00. | <4h 2026-08-07 03:00 | 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 88 / 100 | TESTSRV_4.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-07 01:00. | <4h 2026-08-07 01:00 | 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 88 / 100 | TESTSRV_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-07 01:00. | <4h 2026-08-07 01:00 | 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 88 / 100 | TESTSRV_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-06 23:00. | <4h 2026-08-06 23:00 | 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 88 / 100 | TESTSRV_4.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-06 23:00. | <4h 2026-08-06 23:00 | 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 88 / 100 | TESTSRV_3.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-06 23:00. | <4h 2026-08-06 23:00 | 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 88 / 100 | TESTSRV_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-06 22:00. | <4h 2026-08-06 22:00 | 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 88 / 100 | TESTSRV_1.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-08-06 22:00. | <4h 2026-08-06 22:00 | 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 88 / 100 | TESTSRV_1.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-08-06 22:00. | <4h 2026-08-06 22:00 | 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 |
| High 80 / 100 | TESTSRV_3.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-07 05:01. SPID 19 | <4h 2026-08-07 05:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 80 / 100 | TESTSRV_5.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-07 01:01. SPID 19 | <4h 2026-08-07 01:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 80 / 100 | TESTSRV_3.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 22:01. SPID 19 | <4h 2026-08-06 22:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 80 / 100 | TESTSRV_2.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 21:01. SPID 19 | <4h 2026-08-06 21:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_4.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 18:01. SPID 19 | <4h 2026-08-06 18:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_3.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 14:01. SPID 19 | <4h 2026-08-06 14:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_1.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 13:01. SPID 20 | <4h 2026-08-06 13:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_2.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 13:01. SPID 19 | <4h 2026-08-06 13:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_3.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 13:01. SPID 19 | <4h 2026-08-06 13:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_4.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 11:01. SPID 19 | <4h 2026-08-06 11:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 78 / 100 | TESTSRV_5.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-08-06 09:01. SPID 19 | <4h 2026-08-06 09:01 | If the blocker repeats, downstream sessions will queue and become application timeouts. | Identify the head blocker, wait type, transaction age, and statement. Tune or reschedule the blocking workload. | blocked_process_report |
| High 72 / 100 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 07:00 | 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 |
| High 72 / 100 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 07:00 | 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 05:00 | 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | 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-08-07 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: SSPI handshake failed with error code 0x80090301, state 14 while establishing a connection with inte SSPI handshake failed with error code 0x80090301, state 14 while establishing a connection with inte | <24h 2026-08-07 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 04:00 | 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 03:00 | 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 02:00 | 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 02:00 | 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 01:00 | 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 01:00 | 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-07 00:00 | 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 |
| High 70 / 100 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 23:00 | 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 23:00 | 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 |
| High 70 / 100 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 22:00 | 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 |
| High 70 / 100 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 21:00 | 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 21:00 | 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 |
| High 70 / 100 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 20:00 | 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 |
| High 70 / 100 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Network error code 0x2745 occurred while establishing a connection; the connection has been closed. Network error code 0x2745 occurred while establishing a connection; the connection has been closed. | <24h 2026-08-06 19:38 | 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 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 19:00 | 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 19:00 | 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 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 19:00 | 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 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 19:00 | 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 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 18:00 | 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 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 18:00 | 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 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 17:00 | 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 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 16:00 | 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 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 15:00 | 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 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 14:00 | 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 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 12:00 | 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 12:00 | 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 11:00 | 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 | TESTSRV_1.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 11:00 | 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 | TESTSRV_3.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 11:00 | 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 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 10:00 | 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 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 07:00 | 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 | TESTSRV_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 06:00 | 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 | TESTSRV_4.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 05:00 | 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 | TESTSRV_5.DBNEXIA.COM - | 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-08-06 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 04:00 | 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-06 01:00 | 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 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro Login failed for user 'DBAChaos_Invalid_Login'. Reason: Could not find a login matching the name pro | <24h 2026-08-05 23:00 | 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 58 / 100 | TESTSRV_1.DBNEXIA.COM DBAChaos | Queries | Long running session 0 DBAChaos. 72s elapsed. Wait completed cached query. Blocked by - | <12h latest sample | A long runner can become blocking, log growth, tempdb growth, or user-facing timeout if it keeps accumulating work. | Inspect the execution plan and wait type. If it is blocking or runaway, coordinate a controlled stop and fix the query path. | sys.dm_exec_requests |
| Warning 58 / 100 | TESTSRV_4.DBNEXIA.COM DBAChaos | Queries | Long running session 0 DBAChaos. 71s elapsed. Wait completed cached query. Blocked by - | <12h latest sample | A long runner can become blocking, log growth, tempdb growth, or user-facing timeout if it keeps accumulating work. | Inspect the execution plan and wait type. If it is blocking or runaway, coordinate a controlled stop and fix the query path. | sys.dm_exec_requests |
| Warning 58 / 100 | TESTSRV_5.DBNEXIA.COM DBAChaos | Queries | Long running session 0 DBAChaos. 71s elapsed. Wait completed cached query. Blocked by - | <12h latest sample | A long runner can become blocking, log growth, tempdb growth, or user-facing timeout if it keeps accumulating work. | Inspect the execution plan and wait type. If it is blocking or runaway, coordinate a controlled stop and fix the query path. | sys.dm_exec_requests |