Respond to SQL Server alarms raised by Spotlight.
Alarms that can be raised against a SQL Server connection
- Backup - Days Since Last Full Backup alarm
- Clusters - File Share Witness Inaccessible alarm
- Clusters - Non-Preferred Node alarm
- Databases - Log File Space Used alarm
- Databases - Unavailable alarm
- Error Log - Fatal Database Integrity Suspect Error (severity level 23) alarm
- Error Log - Fatal Hardware Error (severity level 24) alarm
- Error Log - Fatal Hardware Error (severity level 25) alarm
- Error Log - High Severity Error Log Message alarm
- Error Log - Information Severity Error Log Message alarm
- Index Fragmentation alarm
- LiteSpeed Backup Failed alarm
- LiteSpeed Backup Warning alarm
- Log Shipping - Primary Backup Job alarm
- Log Shipping - Secondary Job alarm
- Log Shipping - Secondary Latency alarm
- Memory - Free System Page Table Entries alarm
- Memory - Page Life Expectancy alarm
- Memory - Percentage Free Virtual Memory alarm
- Memory - Physical Memory Available alarm
- Mirroring - Unrestored Log alarm
- Mirroring - Unsent Log alarm
- Network - Percentage Bandwidth alarm
- Network - SQL Server Packets Error Rate alarm
- Paging - Disk Activity alarm
- Paging - File Collision alarm
- Performance Investigator alarm
- Poor Performance Health Alarm
- SQL - Long Running SQL alarm
- SQL - Running out of Threads alarm
- SQL Agent - Alerts alarm
- SQL Agent - Jobs Failed alarm
- SQL Agent - Long Running Jobs (Percent) alarm
- SQL Agent - Long Running Jobs (Time) alarm
- SQL Agent - Status alarm
- SQL Virtual Log Files Count alarm
- Services - DTC Service Status alarm
- Services - Full Text Search alarm
- Services - Integration Service Status alarm
- Services - Reporting Service Status alarm
- Tempdb Auto Growth alarm
- Tempdb Growth Settings alarm
- Tempdb Number of Files alarm
- Tempdb Version Store Size alarm
- User - Response Time alarm
- Backup - Hours Since Last Differential Backup alarm
- Backup - Minutes Since Last Log Backup alarm
- Clusters - Failed Over alarm
- Clusters - Node Unavailable alarm
- Compiles - Percentage Recompilations alarm
- Databases - Data File Group About to Grow
- Databases - Data File Group Space Used alarm
- Databases - Dynamic Data File Group Growths Remaining alarm
- Databases - Dynamic Log File Growths Remaining alarm
- Databases - Log Flush Wait Time Alarm
- Databases - SQL I/O Errors alarm
- Error Log - Critical Error (severity level lower than 20) alarm
- Error Log - Error Count alarm
- Error Log - Fatal Current Process Error (severity level 20) alarm
- Error Log - Fatal Database (dbid) Processes Error (severity level 21) alarm
- Error Log - Fatal Table Integrity Suspect Error (severity level 22) alarm
- Error Log - Low Severity Error Log Message alarm
- Error Log - Medium Severity Error Log Message alarm
- I/O Stall Time alarm
- Index Fragmentation Status alarm
- Latch - Total Wait Time Rate alarm
- Locks - Blocked Processes alarm
- Locks - Deadlocks alarm
- Mirroring - Failedover alarm
- Mirroring - State alarm
- Missing SQL Performance Counters alarm
- Monitored Server - SQL Server Alarm Action Failure alarm
- Monitored Server - SQL Server Alarm Evaluation Failure alarm
- Monitored Server - SQL Server Collection Execution Failure alarm
- Monitored Server - SQL Server Connection Failure alarm
- Monitored Server - SQL Server Host Not Defined alarm
- Monitored Server - SQL Server Planned Outage alarm
- Monitored Server - SQL Server Secondary Connection Failure alarm
- Monitored Server - SQL Server Unsupported Version alarm
- SQL Custom Counters alarm
- Tempdb Contention alarm
- Tempdb File Location alarm
- Tempdb File Size alarm
- Tempdb Version Store Generation Rate Alarm
- User - Connection Count alarm
- User - Logins Per Second alarm
How to acknowledge an alarm
If an alarm is configured to require acknowledgment then each raised instance of the alarm remains present in Spotlight until it is acknowledged.
- Acknowledge alarms in Spotlight Cloud Mobile
- Acknowledge alarms in Spotlight Enterprise
- Alarms FAQ on the Spotlight Cloud web site
How to snooze an alarm
To snooze an alarm is to temporarily remove the visual alert associated with an alarm.
How to configure an alarm
See Configure Alarms to set the thresholds and severities that determine when an alarm is raised. Disable an alarm. Set an alarm to require acknowledgment. Configure keyed alarms. Collect additional diagnostic information on an alarm.
See Configure Alarm Actions to setup actions for Spotlight to take when an alarm is raised. The actions Spotlight can take include running a program and sending an email. Conditions on taking the action can be defined, such as the day of the week, the time of day, the severity of the alarm, the alarm type and the connection type.
Alarms not supported when SQL Server 2017 and above is hosted on Linux
See Partial support for monitoring SQL Server: SQL Server 2017 and above hosted on Linux.