SQL Server
6sources cover it
4themes fed
4signals shown
Livestatus
Service crashes, backup-writer health and storage pressure on SQL Server hosts.
Signals below are scored for SQL Server today.
How the agent recognizes this workload
- The SQL Server and SQL Server Agent services are present on the host.
- A named instance service such as MSSQL$PAYROLL is present.
- A SQL Server VSS writer service is present and reports state during a backup.
What covers it
| Source | What it is | Status |
|---|---|---|
| Windows Application event log | The Application channel: application crashes and hangs, database and VSS provider faults, certificate and identity-sync failures. | Live |
| Windows System event log | The System channel: service, driver, disk, network, cluster and hardware faults from the operating system itself. | Live |
| Windows services | Service configuration and run state, including automatic services that are not running. | Live |
| Processes | Per-process cost: CPU, working set, handles and sustained growth. | Live |
| Disk volumes | Every fixed volume: free space, fill trend, protection state and whether the filesystem is readable. | Live |
| VSS writers | VSS writer state, the canonical evidence behind a failed backup. | Live |
Signals tagged to it
| Signal | Where it comes from |
|---|---|
mssql db io failed (mssql_db_io_failed) | Windows Application event log |
mssql db page corruption (mssql_db_page_corruption) | Windows Application event log |
mssql db read retried (mssql_db_read_retried) | Windows Application event log |
vss writer failed (vss_writer_failed) | Windows Application event log |