Response horizonwhen to act
3now
85today
0planned
Incident Workspace / Signals
Incident Workspace
88 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-11-09 12:52:34
5 / 5 servers healthy
Critical
26
Needs DBA ownership now
High
0
Likely to repeat or escalate
Next 24h
88
Prevent before next cycle
Servers with risk
5
88 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 load113h
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
23restore readiness
2workload triage
60access/connectivity
0collector repair
AI triage
Recommended focus
Next best action
100
TESTSRV_1.DBNEXIA.COM: Group the latest EventLog rows by first error, error number/state, database, host, application and SQL text. Fix the earliest specific failure in each chain rather than the final generic symptom.
Correlated risk
100
TESTSRV_1.DBNEXIA.COM has 21 concurrent signals across Runtime, Backup, Security, Queries. Treat it as one incident candidate, not separate noise.
Recovery readiness
84
23 backup risk(s) need attention before they become restore or data-loss exposure.
Evidence-based causal analysis
Likely mechanism—not assumed root cause
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
88 prioritized signals
| Risk | Server | Category | Signal | ETA | Forward risk | Next DBA action | Source |
|---|---|---|---|---|---|---|---|
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM - | Runtime | Event pressure is rising 2,701 signals in 24h. Main driver: errors (2,701). | Now 2026-11-08 21:31 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Group the latest EventLog rows by first error, error number/state, database, host, application and SQL text. Fix the earliest specific failure in each chain rather than the final generic symptom. | EventLog |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM - | Runtime | Event pressure is rising 2,579 signals in 24h. Main driver: errors (2,579). | Now 2026-11-08 21:31 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Group the latest EventLog rows by first error, error number/state, database, host, application and SQL text. Fix the earliest specific failure in each chain rather than the final generic symptom. | EventLog |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM - | Runtime | Event pressure is rising 2,595 signals in 24h. Main driver: errors (2,595). | Now 2026-11-08 21:31 | Without triage this can turn into failed jobs, user timeouts, or repeated incident noise during the next business cycle. | Group the latest EventLog rows by first error, error number/state, database, host, application and SQL text. Fix the earliest specific failure in each chain rather than the final generic symptom. | EventLog |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DOM_ForestDream_BD6D | Backup | Backup exposure: DOM_ForestDream_BD6D FULL. FULL 12d ago, LOG 278h ago | <4h 2026-10-28 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DOM_ShadowWhisper_67B1 | Backup | Backup exposure: DOM_ShadowWhisper_67B1 FULL. FULL 12d ago, LOG 278h ago | <4h 2026-10-28 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DOM_DreamBlossom_D66E | Backup | Backup exposure: DOM_DreamBlossom_D66E FULL. FULL 12d ago, LOG 278h ago | <4h 2026-10-28 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DOM_BlossomWhisper_FDD3 | Backup | Backup exposure: DOM_BlossomWhisper_FDD3 FULL. FULL 12d ago, LOG 278h ago | <4h 2026-10-28 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DOM_ThunderMoon_622B | Backup | Backup exposure: DOM_ThunderMoon_622B FULL. FULL 12d ago, LOG 278h ago | <4h 2026-10-28 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_db SIMPLE. FULL 12d ago | <4h 2026-10-28 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_1.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos SIMPLE. FULL 12d ago | <4h 2026-10-28 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DOM_MoonCrystal_16FD | Backup | Backup exposure: DOM_MoonCrystal_16FD FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DOM_ForestSky_5A7D | Backup | Backup exposure: DOM_ForestSky_5A7D FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DOM_WhisperEcho_929E | Backup | Backup exposure: DOM_WhisperEcho_929E FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DOM_CrystalStone_911A | Backup | Backup exposure: DOM_CrystalStone_911A FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DOM_ShadowMoon_946A | Backup | Backup exposure: DOM_ShadowMoon_946A FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DOM_ShadowOcean_4486 | Backup | Backup exposure: DOM_ShadowOcean_4486 FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DOM_ForestEcho_B4A4 | Backup | Backup exposure: DOM_ForestEcho_B4A4 FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DOM_FlameCrystal_07F4 | Backup | Backup exposure: DOM_FlameCrystal_07F4 FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DOM_DreamStone_5722 | Backup | Backup exposure: DOM_DreamStone_5722 FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DOM_ShadowRiver_9AF6 | Backup | Backup exposure: DOM_ShadowRiver_9AF6 FULL. FULL 43d ago, LOG 1022h ago | <4h 2026-09-27 22:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Inspect and repair the log-backup chain, confirm that the recovery model and RPO are intentional, then verify a new log backup and test point-in-time recovery on an isolated instance. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_db SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_db SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_5.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_3.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_5.DBNEXIA.COM dbNexia_db | Backup | Backup exposure: dbNexia_db SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Critical 100 / 100 | TESTSRV_2.DBNEXIA.COM DBAChaos | Backup | Backup exposure: DBAChaos SIMPLE. FULL 43d ago | <4h 2026-09-27 02:00 | Restore point confidence is degrading. A real outage can become data-loss work instead of normal recovery. | Correct the full-backup job or destination, create a new successful full backup, run media verification and prove recovery with an isolated test restore. | msdb.dbo.backupset |
| Warning 68 / 100 | TESTSRV_2.DBNEXIA.COM - | Security | Login failure pattern LGIF: Network error code 0xe8 occurred while establishing a connection; the connection has been closed. Th Network error code 0xe8 occurred while establishing a connection; the connection has been closed. Th | <24h 2026-11-01 11:35 | 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: 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-10-11 20:37 | 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: 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-10-07 22:06 | 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: Network error code 0x2746 occurred while establishing a connection; the connection has been closed. Network error code 0x2746 occurred while establishing a connection; the connection has been closed. | <24h 2026-09-27 21:13 | 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: Network error code 0x2746 occurred while establishing a connection; the connection has been closed. Network error code 0x2746 occurred while establishing a connection; the connection has been closed. | <24h 2026-09-27 21:13 | 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: 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-09-26 19:50 | 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: [REDACTED: sensitive statement] [REDACTED: sensitive statement] | <24h 2026-09-20 13:11 | 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: [REDACTED: sensitive statement] [REDACTED: sensitive statement] | <24h 2026-09-20 13:11 | 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: [REDACTED: sensitive statement] [REDACTED: sensitive statement] | <24h 2026-09-20 13:11 | 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: [REDACTED: sensitive statement] [REDACTED: sensitive statement] | <24h 2026-09-20 13:11 | 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: [REDACTED: sensitive statement] [REDACTED: sensitive statement] | <24h 2026-09-20 13:11 | 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-20 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-20 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-20 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-09-20 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-09-20 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-09-20 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-09-20 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-20 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-09-20 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_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-20 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 |
| 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-20 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 |
| 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-20 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 |
| 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-20 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 |
| 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-20 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-09-20 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_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-20 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_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-20 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_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-20 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_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-20 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_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-20 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-09-20 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 |
| 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-09-20 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 |
| 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-09-20 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 |
| 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-20 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 |
| 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-20 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-09-20 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 |
| 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-09-20 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 |
| 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-19 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_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-19 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-19 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 |
| 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-19 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 |
| 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-19 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_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-19 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_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-19 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-19 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-19 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_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-19 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-19 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_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-19 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_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-19 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-19 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-09-19 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-19 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 |
| 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-19 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 |
| 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-09-19 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_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-19 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_5.DBNEXIA.COM - | Security | Login failure pattern LGIF: Network error code 0xe8 occurred while establishing a connection; the connection has been closed. Th Network error code 0xe8 occurred while establishing a connection; the connection has been closed. Th | <24h 2026-09-19 06:10 | 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-09-19 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-09-19 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 59 / 100 | TESTSRV_2.DBNEXIA.COM dbNexia_db | Queries | Long running session 65 dbNexia_db. 96s elapsed. Wait -. 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 59 / 100 | TESTSRV_1.DBNEXIA.COM dbNexia_db | Queries | Long running session 68 dbNexia_db. 95s elapsed. Wait CXSYNC_PORT. 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 |