Alarms that can be raised against an Azure SQL Managed instance connection
- CPU Time Percentage Used
- 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
- Memory - Free System Page Table Entries alarm
- Memory - Page Life Expectancy alarm
- Memory - Percentage Free Virtual Memory alarm
- Memory - Physical Memory Available alarm
- Network - Azure SQL Managed Instance Packets Error Rate alarm
- Network - Percentage Bandwidth 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 - Jobs Failed alarm
- SQL Agent - Long Running Jobs (Percent) alarm
- SQL Agent - Long Running Jobs (Time) alarm
- SQL Virtual Log Files Count alarm
- Services - Full Text Search alarm
- Storage Free Space
- Storage Percentage Used
- Tempdb Auto Growth alarm
- Tempdb Version Store Size alarm
- User - Response Time 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
- Missing SQL Performance Counters alarm
- Monitored Server - Azure SQL Managed Instance Alarm Action Failure alarm
- Monitored Server - Azure SQL Managed Instance Alarm Evaluation Failure alarm
- Monitored Server - Azure SQL Managed Instance Collection Execution Failure alarm
- Monitored Server - Azure SQL Managed Instance Connection Failure alarm
- Monitored Server - Azure SQL Managed Instance Host Not Defined alarm
- Monitored Server - Azure SQL Managed Instance Planned Outage alarm
- Monitored Server - Azure SQL Managed Instance Secondary Connection Failure alarm
- SQL Custom Counters alarm
- Tempdb Contention 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. For detailed information, see Acknowledge alarms in Spotlight Enterprise.
How to snooze an alarm
To snooze an alarm is to temporarily remove the visual alert associated with an alarm. For detailed information, see Snooze alarms in Spotlight Enterprise.
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.