Alarms raised under a Spotlight Cloud Basic subscription
- Azure SQL MI - Job Failed alarm
- User - Response Time alarm
- Memory - Page Life Expectancy alarm
- Resource - Storage Free Space
- Resource - CPU Time Percentage Used
- Resource - Storage Percentage Used
- Services - DTC Service Status alarm
- Services - Full Text Search alarm
- Services - Integration Service Status alarm
- Services - Reporting Service Status alarm
- Services - SQL Agent Mail Status alarm
- SQL Agent - Alerts alarm
- TempDB - Contention alarm
- TempDB - Space Used in General Purpose Tier
- Databases - Data File Group Space Used alarm
- Databases - Dynamic Data File Group Growths Remaining alarm
- Databases - Unavailable alarm
Alarms raised under a Spotlight Cloud Professional subscription
Requires Spotlight Cloud ProfessionalAzure SQL MI - Job Failed alarm
Raised when a job fails.
Compiles - Percentage Recompilations alarm
Raised when the average ratio between the number of recompiles and the total number of compiles exceeds a threshold. This value is taken over a specific number of background collections.
Databases - Data File Group about to grow alarm
Raised when a file in the disk group is about to grow.
Databases - Log Flush Wait Time alarm
Raised when the duration of the last log flush for a database exceeds a threshold.
Databases - SQL I/O Errors alarm
Raised when I/O errors are encountered by SQL Server.
Databases - Unavailable alarm
Raised when a SQL Server database is not available for reading. Users attempting to access an unavailable database will receive an error message.
Error Log - Error Count alarm
Raised when Spotlight Cloud detects messages that could become potential problems in the SQL Server error log, SQL Server Agent error log or Windows event logs. To configure Spotlight Cloud to detect these messages, see configure error log.
Error Log - Critical Error (severity level lower than 20)
Raised when SQL Server experiences a new informational error.
Error Log - Fatal Current Process Error (severity level 20)
Raised when SQL Server experiences a new fatal error of severity level 20. It indicates that a statement has encountered a problem.
Error Log - Fatal Database (dbid) Process Error (severity level 21)
Raised when SQL Server experiences a new fatal error of severity level 21. It indicates that a problem has been encountered that affects all tasks in the current database, but it is unlikely that the database itself has been damaged.
Error Log - Fatal Table Integrity Suspect Error (severity level 22)
Raised when SQL Server experiences a new fatal error message of severity level 22. It might indicate that the table or index specified in the message has been damaged by a software or hardware problem.
Error Log - Fatal Database Integrity Suspect Error (security level 23)
Raised when SQL Server experiences a new fatal error message of severity level 23. It indicates that the integrity of the entire database is in question because of a hardware or software problem.
Error Log - Fatal Hardware Error (severity level 24)
Raised when SQL Server experiences a new fatal error message of severity level 24. It indicates a media failure.
Error Log - Fatal Hardware Error (severity level 25)
Raised when SQL Server experiences a new fatal error message of severity level 25. It indicates a system error.
Relevant only for SQL Server 2012 and earlier versions.
Error Log - High Severity Error Log Message
Raised when the SQL Server Agent experiences a new critical error.
Error Log - Medium Severity Error Log Message
Raised when the SQL Server Agent experiences a new warning error.
Error Log - Low Severity Error Log Message
Raised when the SQL Server Agent experiences a notice error.
Error Log - Information Severity Error Log Message
Raised when the SQL Server Agent experiences a new informational error.
I/O Stall Time alarm
Raised when the average I/O wait time for any database file exceeds a threshold. This value is taken over a specific number of background collections.
Index Fragmentation alarm
Raised when the largest index partition on the SQL Server is more than 5% fragmented. It is a good idea to defragment large index partitions that are more than 5% fragmented. By default, only partitions that have more than 1000 pages, and 5 or more scan or update operations, are taken into consideration. To configure the defaults, see configure fragmentation checks.
Locks - Blocked Processes alarm
Raised when a process is blocked for longer than a predefined threshold. The default is 120 seconds. Excessive blocking can be a major cause of poor application performance.
Locks - Deadlocks alarm
Raised when the number of deadlocks detected since the previous data collection exceeds a threshold. A Deadlock occurs when multiple SQL Server sessions request conflicting locks in such a way that two locks are blocked by each other.
Locks - Long Duration Block alarm
Raised when the amount of time for which a specific process in a SQL Server instance has been blocked exceeds a predefined threshold. Excessive blocking can be a major cause of poor application performance.
Memory - Page Life Expectancy alarm
Raised when the page life expectancy falls below a threshold.
Monitored Server - Azure SQL MI Alarm Action Failure alarm
Raised when a configured Alarm Action failed to evaluate.
Monitored Server - Azure SQL MI Alarm Evaluation Failure alarm
Raised when Spotlight Cloud failed to evaluate a given alarm from a given collection.
Monitored Server - Azure SQL MI Collection Execution Failure alarm
Raised when a given collection failed to execute against the monitored server.
Monitored Server - Azure SQL MI Connection Failure alarm
Raised when Spotlight Cloud fails to connect to the Azure SQL Managed Instance.
Monitored Server - Azure SQL MI Planned Outage alarm
Raised during a planned outage of the connection, and cleared upon its completion.
Monitored Server - Azure SQL MI Secondary Connection Failure alarm
Raised when the Azure SQL Managed Instance is not responding.
Network - SQL Server Packets Error Rate alarm
Raised when the rate at which SQL Server is encountering network packet errors exceeds a threshold.
Resource - Storage Free Space
Raised when the Azure SQL MI storage free space falls below a threshold.
Resource - CPU Time Percentage Used
Raised when used CPU time, averaged over the 3 most recent data samples, and divided by the service tier limit, exceeds a threshold.
Resource - Storage Percentage Used
Raised when the percentage of space that is allocated to the Azure SQL MI in use exceeds a threshold.
SQL Agent - Alerts alarm
Raised when at least one SQL Agent alert has occurred in the last few minutes.
SQL Agent - Long Running Job (Time) alarm
Raised when a SQL Agent job has been running longer than its average running time.
SQL Agent - Long Running Job (Percent) alarm
Raised when a SQL Agent job has been running for considerably longer than expected for SQL Agent jobs of its type.
SQL - Long Running SQL alarm
Raised when SQL has been running longer than a configured time. Because the (configured time) is unique to each environment, the SQL - Long Running SQL alarm is not configured by default.
SQL Virtual Log Files Count alarm
Raised when the count of Virtual Log Files (VLFs) is excessive. A high number can have a major impact on SQL start up times and database restores.
Tempdb Contention alarm
Raised when Tempdb is experiencing contention.
TempDB - Space Used in General Purpose Tier
Raised when TempDB storage space is nearing its full capacity. It is raised for the General Purpose service tier only.
Tempdb Version Store Generation Rate alarm
Raised when the Tempdb Version Store growth rate is high compared to the cleanup rate.
Tempdb Version Store Size alarm
Raised when the Tempdb version store is too large for the monitored environment.
User - Connection Count alarm
Raised when the number of users connected exceeds a threshold.
User - Logins Per Second alarm
Raised when the average number of logins per second exceeds a threshold. This value is taken over a specific number of background collections.
User - Response Time alarm
Raised when the time taken for Spotlight Cloud to send a simple query to the monitored SQL Server instance, have it processed and get the answer back is more than the configured threshold. The response time alarm does not tell you where the time is spent; it could be the network or it could be the SQL Server instance is unresponsive.