Action Center

One queue for operational work

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

2026-07-04 07:36 24h lookback
Critical8
High18
Watch0
Due now/today26
Affected servers5
Total servers5
Severity shape26 open
Critical
8
High
18
Watch
0
Work categoriestop drivers
Backup
20
Runtime
3
SQL Agent
2
Concurrency
1
Immediacy26 due now/today
26 immediate 0 planned
Owner loadassignment view
DBA
23
DBA / App owner
3
SLA bucketsplanning pressure
Today
26
Source pageswhere to investigate
Backup Readiness 20 AI Incidents 4 Server Overview 2
Priority queue26 open signals
High210
DOM_BlossomWhisper_FDD3 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_BlossomWhisper_FDD3 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_BlossomWhisper_FDD3 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
High210
DOM_DreamBlossom_D66E backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_DreamBlossom_D66E backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_DreamBlossom_D66E backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
High210
DOM_ForestDream_BD6D backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ForestDream_BD6D backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestDream_BD6D backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
High210
DOM_ShadowWhisper_67B1 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ShadowWhisper_67B1 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowWhisper_67B1 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
High210
DOM_ThunderMoon_622B backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ThunderMoon_622B backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ThunderMoon_622B backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
High210
DOM_DreamStone_5722 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_DreamStone_5722 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_DreamStone_5722 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High210
DOM_ForestEcho_B4A4 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ForestEcho_B4A4 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestEcho_B4A4 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High210
DOM_ForestSky_5A7D backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ForestSky_5A7D backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestSky_5A7D backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High210
DOM_ShadowRiver_9AF6 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ShadowRiver_9AF6 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowRiver_9AF6 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High210
DOM_WhisperEcho_929E backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_WhisperEcho_929E backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_WhisperEcho_929E backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High210
DOM_CrystalStone_911A backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_CrystalStone_911A backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_CrystalStone_911A backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High210
DOM_FlameCrystal_07F4 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_FlameCrystal_07F4 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_FlameCrystal_07F4 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High210
DOM_MoonCrystal_16FD backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_MoonCrystal_16FD backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_MoonCrystal_16FD backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High210
DOM_ShadowMoon_946A backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ShadowMoon_946A backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowMoon_946A backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High210
DOM_ShadowOcean_4486 backup chain needs attention Backup

FULL missing, LOG missing. Full: -, diff: -, log: -.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

database 'DOM_ShadowOcean_4486 backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowOcean_4486 backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical180
dbNexia_db backup chain needs attention Backup

FULL missing. Full: -, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Backup Readiness
Critical180
dbNexia_db backup chain needs attention Backup

FULL missing. Full: -, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
Critical180
dbNexia_db backup chain needs attention Backup

FULL missing. Full: -, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical180
dbNexia_db backup chain needs attention Backup

FULL missing. Full: -, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Backup Readiness
Critical180
dbNexia_db backup chain needs attention Backup

FULL missing. Full: -, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Backup Readiness
Critical90
Error pulse detected Runtime

Errors 988, timeouts 1, login failures 0, CPU warnings 0. The specified @name ('MAL_MAINT_MAINT_JOB') already exists.

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

job 'Error pulse detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

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

Errors 876, timeouts 0, login failures 0, CPU warnings 0. Conversion failed when converting the nvarchar value 'Updated_6959' to data type bit.

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

job 'Error pulse detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

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

Errors 891, timeouts 1, login failures 0, CPU warnings 0. Conversion failed when converting the nvarchar value 'Updated_8226' to data type bit.

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

job 'Error pulse detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_3.DBNEXIA.COM AI Incidents
High76
Deadlock detected Concurrency

2026-07-03 11:55 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-07-03T11:55:15.544Z"><data name="xml_report"><value><deadlock><victim-list><victimProcess ...

Capture the deadlock graph, identify both statements and objects, then fix index support or transaction order so code paths acquire locks consistently.
Users may see failed transactions and retry storms.
Meaning

job 'Deadlock detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: deadlock Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM AI Incidents
High72
dbNexia_Process_Logs SQL Agent

ServerMetrics. 2026-07-04 07:35. Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'dbo.ServerMetrics'. Th...

Open the failing SQL Agent step, classify the exact error type, fix account/path/schema/data/concurrency cause, rerun time-sensitive jobs and confirm next job history succeeds.
Maintenance, ETL, backups or integrity routines may not have completed.
Meaning

database 'dbNexia_Process_Logs' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_Process_Logs'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: job-failure Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Server Overview
High72
MAL_MAINT_Process_Logs SQL Agent

ServerMetrics. 2026-07-04 07:10. Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'dbo.ServerMetrics'. Th...

Open the failing SQL Agent step, classify the exact error type, fix account/path/schema/data/concurrency cause, rerun time-sensitive jobs and confirm next job history succeeds.
Maintenance, ETL, backups or integrity routines may not have completed.
Meaning

database 'MAL_MAINT_Process_Logs' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'MAL_MAINT_Process_Logs'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Rule: job-failure Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Server Overview