Response horizonwhen to act
5now
92today
0planned
AI Incident Prevention
AI Incident Center
97 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-09-02 11:00:55
5 / 5 servers healthy
Critical
30
Needs DBA ownership now
High
45
Likely to repeat or escalate
Next 24h
97
Prevent before next cycle
Servers with risk
5
97 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 load149h
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
0restore readiness
32workload 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 18 concurrent signals across Runtime, Concurrency, Security. Treat it as one incident candidate, not separate noise.
Concurrency forecast
82
30 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
97 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,271 signals in 24h. Main driver: errors (2,865). | Now 2026-09-02 10:14 | 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,185 signals in 24h. Main driver: errors (2,779). | Now 2026-09-02 10:14 | 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_4.DBNEXIA.COM - | Runtime | Event pressure is rising 218 signals in 24h. Main driver: timeouts (112). | Now 2026-09-02 10:14 | 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_5.DBNEXIA.COM - | Runtime | Event pressure is rising 206 signals in 24h. Main driver: timeouts (104). | Now 2026-09-02 10:14 | 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_2.DBNEXIA.COM - | Runtime | Event pressure is rising 3,180 signals in 24h. Main driver: errors (2,779). | Now 2026-09-02 10:14 | 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 90 / 100 | TESTSRV_3.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-09-02 11:00. | <4h 2026-09-02 11: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_3.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-09-02 11:00. | <4h 2026-09-02 11: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_5.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-09-02 11:00. | <4h 2026-09-02 11: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_5.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-09-02 11:00. | <4h 2026-09-02 11: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-09-02 10:00. | <4h 2026-09-02 10: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-09-02 10:00. | <4h 2026-09-02 10: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-09-02 10:00. | <4h 2026-09-02 10: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_4.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-09-02 10:00. | <4h 2026-09-02 10: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_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-09-02 10:00. | <4h 2026-09-02 10: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_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-09-02 10:00. | <4h 2026-09-02 10: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-09-02 10:00. | <4h 2026-09-02 10: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-09-02 10:00. | <4h 2026-09-02 10: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 master | Concurrency | Deadlock detected master / - at 2026-09-02 10:00. | <4h 2026-09-02 10: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-09-02 09:00. | <4h 2026-09-02 09: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-09-02 09:00. | <4h 2026-09-02 09: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-09-02 09:00. | <4h 2026-09-02 09: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 at 2026-09-02 08:00. | <4h 2026-09-02 08: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-09-02 08:00. | <4h 2026-09-02 08: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-09-02 08:00. | <4h 2026-09-02 08: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-09-02 07:00. | <4h 2026-09-02 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 88 / 100 | TESTSRV_2.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-09-02 07:00. | <4h 2026-09-02 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 88 / 100 | TESTSRV_4.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-09-02 06:00. | <4h 2026-09-02 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_4.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health at 2026-09-02 06:00. | <4h 2026-09-02 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_1.DBNEXIA.COM master | Concurrency | Deadlock detected master / - at 2026-09-02 03:00. | <4h 2026-09-02 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_1.DBNEXIA.COM - | Concurrency | Deadlock detected - / system_health file at 2026-09-02 03:00. | <4h 2026-09-02 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 |
| High 82 / 100 | TESTSRV_2.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-09-02 11:00. SPID 64 | <4h 2026-09-02 11:00 | 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 82 / 100 | TESTSRV_4.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-09-02 09:01. SPID 19 | <4h 2026-09-02 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 80 / 100 | TESTSRV_4.DBNEXIA.COM DBAChaos | Concurrency | Blocking chain observed DBAChaos / WIN-PN3T1M2LOOO at 2026-09-02 08:01. SPID 19 | <4h 2026-09-02 08: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-09-01 23:01. SPID 19 | <4h 2026-09-01 23: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-09-01 11:01. SPID 19 | <4h 2026-09-01 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 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-09-02 09: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-09-02 09: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-09-02 08: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-09-02 08: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-09-02 08: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-09-02 08: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-09-02 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_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-09-02 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 |
| 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-09-02 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 |
| 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-09-02 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 |
| 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-09-02 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 |
| 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-09-02 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_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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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-09-02 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 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-09-02 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-09-02 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_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-09-02 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_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-09-02 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_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-09-02 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-09-02 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_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-09-01 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 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-09-01 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 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-09-01 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 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-09-01 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 |
| 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-09-01 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 |
| 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-09-01 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_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-09-01 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-09-01 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-09-01 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_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-09-01 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_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-09-01 13: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-09-01 13: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-09-01 13: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-09-01 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_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-09-01 08: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-09-01 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_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-09-01 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: 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-09-01 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: 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-09-01 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: 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-09-01 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 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 |