The following is a summary of rules available out-of-the-box with the SQL Server 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:
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the SQL Server ADH Service is installed but not running.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the database is not marked as synchronized in the cluster, and is therefore not ready for a planned manual failover.
This alarm is invoked when the data synchronization state is NOT SYNCHRONIZING, or if the state is not SYNCHRONIZED for the synchronous-commit group database.
This alarm is raised when availability group estimated time for failover (RTO) exceeds a predefined threshold.
This alarm is raised when availability group estimated time for failover (RTO) baseline deviation is detected.
This alarm is invoked when the availability group listener IP is offline, either because it is being brought online or because it failed to be brought online.
This alarm is invoked when the availability group failed over to one of its secondary replicas.
This alarm is raised when availability group potential data loss (RPO) exceeds a predefined threshold.
This alarm is raised when availability group potential data loss (RPO) baseline deviation is detected.
This alarm is invoked when the availability group replica is disconnected, and is therefore not ready for a failover.
This alarm is invoked when the availability replica is unable to read or write from the cluster.
This alarm is invoked when the data synchronization state is NOT SYNCHRONIZING, or if the state is not SYNCHRONIZED for the synchronous-commit database replica.
This alarm is invoked when there is not enough space on the media for the backup.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the buffer cache hit rate falls below a predefined threshold.
This alarm is invoked when the percentage of free buffer pages falls below a predefined threshold.
This alarm is invoked when potentially unsafe CLR Assemblies are detected in one of the instance’s databases.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the SQL Server cluster group’s active node has moved from one node to another.
This alarm is invoked when Foglight data collection has failed.
This alarm is invoked when the average connection time to the instance exceeds a predefined threshold.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the value of the occupied cache percent parameter exceeds a predefined threshold, indicating data modifications are not being propagated in a timely manner to the Mirroring database.
This alarm is invoked upon any modification of the role description at a Principal or Mirror database.
This alarm is invoked upon any modification of the mirroring status of the Principal or Mirror database.
This alarm is invoked upon any modification of the mirror witness server’s status.
This alarm is invoked when the number of days that have elapsed since the last valid full and differential database backup exceeds a predefined threshold.
This alarm is invoked when no valid full backup date is found for a database.
This alarm is invoked when the SQL Server instance has experienced a deadlock or deadlock chain.
This alarm is invoked when the number of deadlocks encountered by a specific SQL Server instance exceeds a predefined threshold.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a specific disk has an I/O requests queue length higher than threshold, indicating high competition on disk access.
This alarm is invoked when the Distributed Transaction Coordinator (DTC) service is installed but not running.
This alarm is invoked when the error log file size exceeds a predefined value, making the log file too large to scan.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a database data file group is nearing its full capacity.
This alarm is invoked when the Full Text Search service (MSSearch) is installed but not running.
This alarm is invoked when the number of hours that have elapsed since the last valid log database backup exceeds a predefined threshold.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the SQL Server instance is not running (down) or non-responsive.
This alarm is invoked when the SQL Server Integration Service is installed but not running.
This alarm is invoked upon detecting a job failure within a SQL Server instance.
This alarm is invoked when a SQL Server instance job retry is detected.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when SQL Server exceeds a predefined threshold of lock timeouts.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a database log file is reaching its full capacity.
This alarm is invoked when the duration of the average log flush for a database exceeds a predefined threshold.
This alarm is invoked upon encountering log shipping failure.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the amount of time for which a specific process in a SQL Server instance has been blocked exceeds a predefined threshold.
This alarm is invoked when a job’s execution time proportionately exceeds average execution time by a given threshold.
This alarm is invoked when a session’s execution time exceeds a predefined threshold (requires PI to be installed and activated).
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when at least one node in a cluster is reported as not running (down).
This alarm is raised when Foglight for SQL Server detects that SQL Server is not running on its preferred cluster node.
This alarm is invoked when the OLAP service is installed but not running.
This alarm is invoked when a cluster node is offline, possibly caused by an OS cluster service issue or malfunction at the cluster quorum.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the buffer cache page life expectancy falls below a predefined threshold.
This alarm is invoked when the rate per second of page splits per Batch Executions within a SQL Server instance exceeds a predefined threshold.
This alarm is invoked when the host’s percentage of free virtual memory falls below a predefined threshold.
This alarm is invoked when the compilation rate exceeds a predefined threshold value, indicating either an inadequately small procedure cache or excessive use of dynamic code.
This alarm is invoked when the plan cache hit rate falls below a predefined threshold.
This alarm is invoked when the SQL Server process’s CPU consumption exceeds a predefined threshold.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when the delivery latency of a replication agent within a SQL Server instance exceeds a predefined threshold.
This alarm is invoked when a replication agent within a SQL Server instance has a status of ‘Error’, ‘Failed’, or ‘Not Started’.
This alarm is invoked upon detecting failures in SQL Server’s replication process.
This alarm is invoked when the number of hours left until the expiry of a specific publication falls below a predefined threshold.
This alarm is invoked upon detecting errors in a publication within a SQL Server instance involved in a replication process.
This alarm is invoked upon detecting a publication with the status Failed in a SQL Server instance involved in a Replication process.
This alarm is invoked upon detecting the status Failed within a subscription in a SQL Server instance that is involved in a Replication process.
This alarm is invoked when the SQL Server Report Service is installed but not running.
This alarm is invoked when the used memory percentage of the resource pool exceeds the predefined threshold.
This alarm is invoked when the response time exceeds a predefined threshold due to various reasons such as host down, SQL Server down, network issues, or SQL Server overload.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm monitors the retrieve throughput of the SQL Server instance.
This alarm is invoked when the number of SQL Server Agent alerts exceeds a predefined threshold.
This alarm is invoked upon detecting that SQL Server Agent has experienced a new informational error.
This alarm is invoked upon detecting that SQL Server Agent has experienced new log errors.
This alarm is invoked when the SQL Server SQL Browser Service is installed but not running.
This alarm fires when I/O errors have been encountered, possibly indicating a need to check the SQL Server log as such errors can result in loss of data.
This alarm is invoked when the rate per second of packet errors exceeds a predefined threshold.
This alarm is invoked when the change tracking feature, which relies on SQL Server default trace, encounters an error.
This alarm is invoked when data has not been inserted to the performance repository for more than the predefined threshold (default 30 minutes).
This alarm is invoked when the SQL Server Agent is installed but not running.
This alarm is invoked upon detecting that SQL Server has experienced new log errors.
This alarm indicates that a statement has encountered a problem affecting only the current task; the database itself is unlikely to be damaged.
This alarm indicates that a problem has been encountered that affects all tasks in the current database, but the database itself is unlikely to be damaged.
This alarm indicates that the integrity of the entire database is in question because of a hardware or software problem.
This alarm indicates a media failure.
This alarm indicates that the table or index specified in the message has been damaged by a software or hardware problem.
This alarm is invoked upon detecting that SQL Server has experienced new informational error.
This alarm is invoked when the SQL Server Writer Service is installed but not running.
This alarm is invoked when the rate at which a specific SQL Server instance experiences table lock escalations exceeds a predefined threshold.
This alarm is invoked when creating a temporary table raises an error due to space related issues.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when a baseline deviation is detected in this metric in a SQL Server instance.
This alarm is invoked when Foglight is unable to read the free space from the backup media due to insufficient permissions, non-existent location, or unsupported OS command.
This alarm is invoked when a specific database is not available on a SQL Server instance.
This alarm is invoked when the connection to the SQL Server instance failed.
This alarm is invoked when the connection time to the OS exceeds a predefined threshold.
This alarm is invoked when the percentage of Virtualization Overhead exceeds a predefined threshold.
This alarm is invoked when the percentage of Worker Threads used exceeds a predefined threshold, indicating SQL Server is overloaded.
This alarm is invoked when SQL Managed Instance CPU consumption exceeds a predefined threshold.
This alarm is invoked when SQL Managed Instance Memory consumption exceeds a predefined threshold.
This alarm is raised when SQL Managed Instance storage utilization reaches the predefined threshold, which may lead to databases being unable to grow.
This alarm is raised when SQL Managed Instance TempDB data file utilization reaches the predefined threshold, which may cause operations requiring TempDB to stall or fail.
This alarm is raised when SQL Managed Instance TempDB log file utilization exceeds predefined threshold, which may cause operations requiring TempDB to stall or fail.
This alarm is invoked when the agent is not working properly and data is not updated in the repository.