Action Center

Action Center

Prioritized actions from connectivity, backups, storage, jobs, runtime signals, concurrency and telemetry gaps.

2026-09-21 19:03 24h lookback
Critical5
High5
Watch0
Due now/today10
Affected servers5
Total servers5
Severity shape10 open
Critical
5
High
5
Watch
0
Work categoriestop drivers
Runtime
5
Storage
5
Immediacy10 due now/today
10 immediate 0 planned
Owner loadassignment view
DBA / App owner
5
DBA
5
SLA bucketsplanning pressure
Today
10
Source pageswhere to investigate
AI Incidents 5 Forecast 5
Priority queue10 open signals
Critical90
Error pulse detected Runtime

Errors 2660, timeouts 22, login failures 1, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
DBA assessment

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'Error pulse detected', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_1.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2631, timeouts 23, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
DBA assessment

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'Error pulse detected', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_2.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2585, timeouts 21, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
DBA assessment

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'Error pulse detected', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_3.DBNEXIA.COM AI Incidents
Critical88
Error pulse detected Runtime

Errors 23, timeouts 20, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
DBA assessment

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'Error pulse detected', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_4.DBNEXIA.COM AI Incidents
Critical86
Error pulse detected Runtime

Errors 22, timeouts 19, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
DBA assessment

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'Error pulse detected', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_5.DBNEXIA.COM AI Incidents
High78
ANNAT 1 is low on free space Storage

17.7 GB free (44.3%) of 40.0 GB.

Compare current free GB with forecast database, log, TempDB, backup and maintenance demand. Reclaim, relocate or reserve capacity before policy is breached, then verify both free GB and free percent.
Database growth, tempdb, backups or logs can stop the workload.
DBA assessment

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'ANNAT 1 is low on free space', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

17.7 GB free (44.3%) of 40.0 GB.

Compare current free GB with forecast database, log, TempDB, backup and maintenance demand. Reclaim, relocate or reserve capacity before policy is breached, then verify both free GB and free percent.
Database growth, tempdb, backups or logs can stop the workload.
DBA assessment

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'ANNAT 1 is low on free space', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

17.7 GB free (44.3%) of 40.0 GB.

Compare current free GB with forecast database, log, TempDB, backup and maintenance demand. Reclaim, relocate or reserve capacity before policy is breached, then verify both free GB and free percent.
Database growth, tempdb, backups or logs can stop the workload.
DBA assessment

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'ANNAT 1 is low on free space', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

17.7 GB free (44.3%) of 40.0 GB.

Compare current free GB with forecast database, log, TempDB, backup and maintenance demand. Reclaim, relocate or reserve capacity before policy is breached, then verify both free GB and free percent.
Database growth, tempdb, backups or logs can stop the workload.
DBA assessment

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'ANNAT 1 is low on free space', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

17.7 GB free (44.3%) of 40.0 GB.

Compare current free GB with forecast database, log, TempDB, backup and maintenance demand. Reclaim, relocate or reserve capacity before policy is breached, then verify both free GB and free percent.
Database growth, tempdb, backups or logs can stop the workload.
DBA assessment

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Operational impact

The proven recovery-point objective is outside policy, and the transaction log may continue to grow while successful log backups are absent.

Recommended DBA action

Inspect the latest log-backup job failure for database 'ANNAT 1 is low on free space', then correct the specific cause: unavailable target, service-account access, broken chain, open transaction, replication/availability-group backlog or disk pressure. Run a log backup only after a valid full-backup baseline exists.

Success criteria

Confirm a new successful backup of the required type, run RESTORE VERIFYONLY where appropriate, and perform a scheduled test restore to an isolated instance to prove the recovery path and expected RPO/RTO.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Forecast