The following is a summary of rules available out-of-the-box with the Azure SQL Database cartridge. Default threshold values can be changed or scoped to specific values, generally through registry variables. These rules can be copied, modified, disabled, or customized in a wide variety of ways.
This section describes the following rules:
Rules related to database availability and monitoring agents.
This alarm is invoked when the connection to database failed.
This alarm is invoked when the average connection time to the database exceeds a predefined threshold (Fatal: 40000ms, Warning: 20000ms).
This alarm is invoked when the response time exceeds a predefined threshold, due to one or more of the following reasons: host down, database down, network issues, or database overload.
This alarm is invoked when the connection to the Elastic Pool master database has failed.
This alarm is invoked when Foglight data collection has failed.
This alarm is invoked when agent not working properly and data is not updated in the repository.
Rules related to High Availability and Geo-Replication.
This alarm is raised when maximum concurrent sessions in percentage of the limit of the Elastic Pool service tier exceeds a threshold. This alarm is raised to prevent a situation where number of open sessions reaching Elastic Pool service tier limit, thereby preventing connect to databases (Fatal: 95%, Warning: 85%, Informational: 75%).
Rules related to database data and storage utilization.
This alarm is invoked when a database is in full capacity. This alarm is raised to prevent a situation where a file that fills its current capacity cannot grow enough to resolve this issue, thereby causing the database to hang (Fatal: 85%, Warning: 75%).
This alarm is invoked when an Elastic Pool is reaching current space limit capacity (Fatal: 95%, Warning: 85%, Informational: 75%).
Rules related to CPU, Data I/O, and Log I/O utilization.
This alarm is invoked when a database has reached the CPU limit. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when a database has reached the CPU limit. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when an elastic pool has reached the CPU limit (Fatal: 95%, Warning: 85%, Informational: 70%).
This alarm is invoked when the overall Elastic Pool DTU consumption is exceeding a predefined threshold. Such a state can indicate any of the underlying databases in the pool is consuming high amount of resources and may result in starvation to other databases in the pool (Fatal: 95%, Warning: 85%, Informational: 70%).
This alarm is invoked when a database has reached high data I/O utilization percentage. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when a database has reached high data I/O utilization percentage. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when an Elastic Pool vCore is getting reached to its Data IO limit threshold. This alarm is raised to prevent a situation where the databases in the Elastic Pool consuming high Data IO, thereby causing Data IO load on the Elastic Pool and resource starvation (Fatal: 95%, Warning: 85%, Informational: 70%).
This alarm is invoked when a database has reached high transaction log writes percentage. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when a database has reached high transaction log writes percentage. This alarm is raised to prevent a situation where the database performance is too high using current activity, thereby causing the database to work very slow (Fatal: 85%, Warning: 75%).
This alarm is invoked when an Elastic Pool vCore is getting reached to its Log IO limit threshold. This alarm is raised to prevent a situation where the databases in the Elastic Pool consuming high Log IO, thereby causing IO load on the Elastic Pool and resource starvation (Fatal: 95%, Warning: 85%, Informational: 70%).
Rules related to memory utilization.
No specific memory rules are currently available for Azure SQL Database.
Rules related to resource breakdown, workload trends, tuning, and sessions.
This alarm is invoked when a baseline deviation is detected in this metric in Azure SQL DB.
This alarm is invoked when a baseline deviation is detected in this metric in Azure SQL DB.
This rule converts agent messages to Foglight alerts.
This alarm fires when the agent is unhealthy.
This alarm monitors the global Azure services status.
This alarm monitors the Azure subscription services health status.
This alarm is invoked when Azure Storage Service end-to-end latency exceeds predefined thresholds (Fatal: 10000ms, Warning: 8000ms, Informational: 5000ms).
This alarm is invoked when Azure Storage Service server latency exceeds predefined thresholds (Fatal: 500ms, Warning: 200ms, Informational: 100ms).
This alarm is invoked when Azure Virtual Machine CPU utilization exceeds predefined thresholds (Fatal: 90%, Warning: 80%, Informational: 70%).
This alarm checks Azure Virtual Machine diagnostics settings configuration.
This alarm is invoked when Azure Virtual Machine memory utilization exceeds predefined thresholds (Fatal: 90%, Warning: 80%, Informational: 70%).
This alarm is invoked when Azure Virtual Machine network transfer rate exceeds predefined thresholds (Fatal: 30 MB/s, Warning: 20 MB/s, Informational: 10 MB/s).
This alarm is invoked when Azure Virtual Machine storage IOPS exceeds predefined thresholds (Fatal: 3000, Warning: 2000, Informational: 1000).
This alarm is invoked when Azure Virtual Machine storage transfer rate exceeds predefined thresholds.
This alarm is invoked when Azure region quota usage utilization exceeds predefined thresholds (Fatal: 90%, Warning: 80%).
This alarm is invoked when Azure subscription budget spending exceeds 90% of the allocated budget.