Backup - Days Since Last Full Backup alarm

The Backup - Days Since Last Full Backup Alarm becomes active when Spotlight detects that a full backup on the SQL Server database has never taken place or has not taken place in the last three days.

Backup - Hours Since Last Differential Backup alarm

The Backup - Hours Since Last Differential Backup Alarm becomes active when Spotlight detects that a differential backup of the SQL Server database has never taken place or has not taken place in the last 24 hours.

Backup - Minutes Since Last Log Backup alarm

The Backup - Minutes Since Last Log Backup Alarm becomes active when Spotlight detects that a log backup of the SQL Server database has never taken place or has not taken place in the last 120 minutes. Log backups are useful in keeping transaction logs in reasonable size.

Clusters - Failed Over alarm

The Clusters - Failed Over alarm is raised when a cluster fails over.

Clusters - File Share Witness Inaccessible alarm

The Clusters - File Share Witness Inaccessible alarm is raised when the cluster resource File Share Witness in a clustered service or Cluster Group application failed.

Clusters - Node Unavailable alarm

The Clusters - Node Unavailable Alarm alarm is raised when Spotlight detects that at least one cluster node (computer system) is not currently running as part of the cluster.

Clusters - Non-Preferred Node alarm

The Clusters - Non-preferred Node alarm is raised when Spotlight detects that SQL Server is running on a Windows cluster, and at least one SQL Server instance is not running on its preferred cluster node.

Compiles - Percentage Recompilations alarm

The Compiles - Percentage Recompilations alarm becomes active 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

The Databases - Data File Group About to Grow alarm is raised when a file in the disk group is about to grow. You can use this information to ensure the time the file resizes is suitable; for example at a time of off-peak activity.

Databases - Data File Group Space Used alarm

The Databases - Data File Group Space Used Alarm is raised when a disk group (or the actual disk) is in danger of filling.

Databases - Dynamic Data File Group Growths Remaining alarm

The Databases - Dynamic Data File Group Growths Remaining alarm is raised when the disk space is insufficient for files to keep growing into or the maximum file size (if it is set) is being approached.

Databases - Dynamic Log File Growths Remaining alarm

The Databases - Dynamic Log File Growths Remaining alarm becomes active when a non fixed size log file in any database is in danger of running out of space to grow.

Databases - Log File Space Used alarm

The Databases - Log File Space Used Alarm becomes active when a log in any database is in danger of filling.

Databases - Log Flush Wait Time Alarm

The Databases - Log Flush Wait Time alarm becomes active when the duration of the last log flush for a database exceeds a threshold.

Databases - SQL I/O Errors alarm

The Databases - SQL I/O Errors alarm is raised when I/O errors are encountered by SQL Server.

Databases - Unavailable alarm

The Databases - Unavailable alarm becomes active when Spotlight Enterprise detects that 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

The Error Log - Error Count alarm becomes active when Spotlight Enterprise detects messages that could be potential problems in the SQL Sever error log, SQL Server Agent error log, or the Windows event logs.

Index Fragmentation alarm

The Index Fragmentation alarm is raised when the largest Index file on the SQL Server is more than 5% fragmented. It is a good idea to defragment large index files that are more than 5% fragmented.

Index Fragmentation Status alarm

The Index Fragmentation Status alarm is raised when data cannot be collected.

I/O Stall Time alarm

The I/O Stall Time alarm becomes active 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.

Latch - Total Wait Time Rate alarm

Latches are monitored to help identify performance bottlenecks.

Locks - Blocked Processes alarm

The Locks - Blocked Processes alarm is raised when a block persists for longer than the time specified in the threshold. The default is 120 seconds.

Locks - Deadlocks alarm

The Locks - Deadlocks alarm is raised when the number of deadlocks that have occurred since the previous data collection exceeds a threshold.

Log Shipping - Primary Backup Job alarm

The Log Shipping - Primary Backup Job alarm is raised when the backup job on the primary database is not enabled.

Log Shipping - Secondary Job alarm

The Log Shipping - Secondary Job alarm is raised when a secondary copy or restore job is not enabled.

Log Shipping - Secondary Latency alarm

The Log Shipping - Secondary Latency alarm is raised when the amount of time that elapsed between the log backup being created on the primary database and restored on the secondary database exceeds a threshold.

Memory - Free System Page Table Entries alarm

The Memory - Free System Page Table Entries (PTE) alarm is raised when this performance counter falls below a threshold.

Memory - Page Life Expectancy alarm

The Memory - Page Life Expectancy alarm becomes active when the page life expectancy falls below a threshold.

Memory - Percentage Free Virtual Memory alarm

This alarm is activated when the average free virtual memory drops below a threshold. This value is taken over a specific number of background collections.

Memory - Physical Memory Available alarm

The Memory - Physical Memory Available alarm is activated when the available memory drops below a threshold.

Mirroring - Failedover alarm

The principal database has failed. The mirror has taken over.

Mirroring - Unrestored Log alarm

The Mirroring - Unrestored Log alarm is raised when the size of an unrestored mirroring log on the mirroring database exceeds a threshold.

Mirroring - Unsent Log alarm

The Mirroring - Unsent Log alarm is raised when the size of an unsent mirroring log exceeds a threshold.

Missing SQL Performance Counters alarm

Spotlight uses the SQL Server virtual table sysperfinfo to retrieve data for many of its displays. In some rare cases, this table may not contain information. When this is the case, Spotlight Enterprise will not be able to collect the data it requires, and will display ‘0’ for many of its metrics. Most obvious will be the Memory icons on the Spotlight Overview page, which will show 0 MB of memory used by SQL Server. Also, many of the flows on the Spotlight Overview page will show no activity, and many drilldowns will show incomplete information.

Network - Percentage Bandwidth alarm

The average network bandwidth capacity of the specified network card is nearing the limit where it is saturating the network link. This value is taken over a specific number of background collections.

Network - SQL Server Packets Error Rate alarm

The Network - SQL Server Packets Error Rate alarm becomes active when the rate at which SQL Server is encountering network packet errors exceeds a threshold.

Paging - Disk Activity alarm

This alarm is activated when paging is low, but the average disk activity on a paging file disk is high. This value is taken over a specific number of background collections.

Paging - File Collision alarm

This alarm becomes active when there is more than one paging file on a single physical disk.

Poor Performance Health Alarm

The database is spending too much time waiting for bottlenecks such as locks and latches.

Services - DTC Service Status alarm

This alarm becomes active when this SQL Server supporting service is installed but not active.

Services - Full Text Search alarm

This alarm becomes active when this SQL Server supporting service is installed but not active.

Services - Integration Service Status alarm

This alarm becomes active when this SQL Server supporting service is installed but not active.

Services - Reporting Service Status alarm

This alarm becomes active when this SQL Server supporting service is installed but not active.

Services - SQL Agent Mail Status alarm

This alarm becomes active when there is a problem with SQL Server Agent Mail.

SQL - Long Running SQL alarm

The SQL - Long Running SQL alarm is 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, by default, is not configured.

SQL Agent - Alerts alarm

The SQL Agent - Alerts alarm is raised when Spotlight Enterprise detects that at least one SQL Agent alert has occurred in the last few minutes.

SQL Agent - Jobs Failed alarm

The SQL Agent - Jobs Failed alarm is raised when Spotlight Enterprise detects that at least one SQL Agent job has failed in the last few minutes.

SQL Agent - Long Running Jobs (Percent) alarm

The SQL Agent - Long Running Jobs (Percent) alarm is raised when a SQL Agent job has been running for considerably longer than the average run time for SQL Agent jobs of its type.

SQL Agent - Long Running Jobs (Time) alarm

The SQL Agent - Long Running Jobs (Time) alarm is raised when a SQL Agent job has been running for a long time.

SQL Agent - Status alarm

This alarm becomes active when this SQL Server supporting service is installed but not active.

SQL Custom Counters alarm

The Custom Counters alarm is raised when the values of any of the custom counters you have configured exceed their thresholds or data collection fails.

SQL Virtual Log Files Count alarm

This alarm is raised on the SQL Server | Overview page | Disk Storage panel | Log Files component when the count of Virtual Log Files (VLFs) is excessive.

Tempdb Auto Growth alarm

This alarm is raised when Tempdb is configured to auto grow and a significant number of growth events are detected.

Tempdb Contention alarm

This alarm is raised when Tempdb is experiencing contention

Tempdb File Location alarm

This alarm is raised when Tempdb files are in the same location as other database files and I/O activity is significant and more than one drive is available.

Tempdb File Size alarm

This alarm is raised when files in Tempdb have different physical sizes.

Tempdb Growth Settings alarm

This alarm is raised when Tempdb files have nonidentical growth settings.

Tempdb Number of Files alarm

This alarm is raised when the number of files in the Tempdb database is less than the number of processors and the SQL Server is experiencing contention on Tempdb.

Tempdb Version Store Generation Rate Alarm

This alarm is raised when the Tempdb Version Store growth rate is high compared to the cleanup rate.

Tempdb Version Store Size alarm

This alarm is raised when the Tempdb version store is too large for your environment.

User - Connection Count alarm

The User - Connection Count alarm is raised when the number of users connected exceeds a threshold.

User - Logins Per Second alarm

The User - Logins Per Second alarm is 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

The User - Response Time alarm is raised when the time taken for Spotlight to send a simple query to the monitored SQL Server instance, have it processed and get the answer back is more than 20 seconds (or 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.