Server Overview

Server operations cockpit

Pick a server and read the current story: what happened, what is happening, what happens next, and exactly what to do first.

Critical 2026-10-14 15:17
Critical3
Action3
Watch0
Stable0
Open actions25
Runtime events8319
Telemetry gaps0
Growth0.1 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 83%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
16
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
5
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
8323
Data confidence Telemetry gaps are counted as risk so empty panels are not mistaken for healthy systems.
0
Action

SERVER 4

TESTSRV_4.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 15:15
Health73
Pressure33
TrendDeteriorating
DirectionRising risk
Best advice

P2 Storage: Plan capacity cleanup or extension for volumes below policy. This is first because the trend is not yet critical, but continued growth will reduce the time available for a controlled fix. Pattern: Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.

What happened

In the selected window, 1 volumes dropped below free-space policy; 115 log/runtime events were recorded, latest at 2026-10-14 15:03; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy.

What happens next

The current log pace projects to about 115 runtime events over the next 24 hours. Pressure indicators: 115 projected runtime events in 24 hours, 1 action signals, 1 watch signals. The likely outcome is repeated noise and growing maintenance debt unless an owner closes the action.

Actions to break the trend 2
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
0 Backups
1 Disk
0 Jobs
115 Logs
0 Locks
0 Queries
0 Gaps
1 disk 115 log/runtime
Concrete findings 8
Disk ANNAT 1

12.9 GB free (32.2%) of 40.0 GB.

Logs 58 Errors

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 57 Timeouts

2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB dbNexia_db

0.1 GB current size.

Largest DB DBAChaos

0.0 GB current size.

Resources CPU and memory

CPU 11.0%, memory free 39.2%, users 1, transactions 7.

TempDB Data and log

Data 2.4%, log 18.7%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 15:15, last failed -. Worst disk ANNAT 1 12.9 GB (32.2%). 115 runtime events. 0.0 GB growth. CPU 11.0%, memory free 39.2%.

Recommended action Correlate the latest errors with jobs, application releases, and user traffic.
Pattern Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.
Forecast The current log pace projects to about 115 runtime events over the next 24 hours.
Break the trend recover or extend disk capacity; triage latest log errors.
CPU / memory free 11.0% / 39.2%
TempDB data / log 2.4% / 18.7%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 115 / 115
Backups / disks / jobs 0 / 1 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.1 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.95 GB
Last OK 2026-10-14 15:15
Last failed -
Data quality 100%
Source confidence 0 gaps
AuditLog Available

dbNexia_db.dbo.AuditLog

DbSizes Available

dbNexia_db.dbo.dbsizes

EventLog Available

dbNexia_db.dbo.EventLog

LiveRequests Available

VIEW SERVER STATE permission

MsdbAgent Available

msdb SQL Agent history

MsdbBackup Available

msdb.dbo.backupset

ServerMetrics Available

dbNexia_db.dbo.ServerMetrics

TempDb Available

VIEW SERVER STATE permission

VolumeStats Available

VIEW SERVER STATE permission

Runtime 115 events

Errors 58, timeouts 57, login failures 0, CPU warnings 0, memory grants 0.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 58, timeouts 57, login failures 0, CPU warnings 0, memory grants 0.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 58, timeouts 57, login failures 0, CPU warnings 0, memory grants 0.'. 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.

Backup risks0
BackupsNo risks

No backup risks detected for this server.

Storage1 low volumes
ANNAT 112.9 GB free

32.2% free of 40.0 GB on T:\.

Meaning and fix

Meaning: This signal is abnormal, but the row text is not specific enough to name a single root cause with confidence.

Fix: Use the row values already shown here to filter the related report by the same server, database/job/login and the same time window.

Verify: The signal should stop repeating in the next collection window after the underlying job, permission, backup, or workload issue is fixed.

Growth0.0 GB
dbNexia_db10.0 MB

Log growth inside the selected 24h window.

Meaning and fix

Meaning: This signal is abnormal, but the row text is not specific enough to name a single root cause with confidence.

Fix: Use the row values already shown here to filter the related report by the same server, database/job/login and the same time window.

Verify: The signal should stop repeating in the next collection window after the underlying job, permission, backup, or workload issue is fixed.

Queries and concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
dbNexia_db0.1 GB

Current largest database inventory sample.

DBAChaos0.0 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.