sqlserver Metrics

The following section describes the metrics that can be configured for the SQL Server Monitoring (sqlserver) probe.
uimpga-ga
The following section describes the metrics that can be configured for the SQL Server Monitoring (sqlserver) probe.
Contents
QoS Metrics
The following table describes the checkpoint metrics that are configured on the probe:
The following types of metrics are used:
  • Count
     - Refers to absolute number of events in the interval. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server".
  • Count/sec
     - Refers to absolute number of events in the interval per second. It is calculated as delta between count at the beginning and at the end of the interval, divided by length of the interval in seconds. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server".
  • Gauge
     - Refers to absolute number, describing the actual state of the system. If it describes size, it is in KB or MB, depending on actual size.
  • Ratio
     - Refers to calculated percentage, using interval counts. In the first interval, it is calculated from total counts (as the interval count cannot be calculated).
  • Status
     - Refers to absolute value such as ‘ONLINE’.
  • Average
     - Refers to calculated using interval counts. In the starting interval, it is calculated from absolute counts.
Metric
Units
Description
Version
QOS_SQLSERVER_agent_job_failure
Count
Monitors failed agent jobs in a defined time interval.
Note:
 This monitor does not generate a clear alarm, by default. You can change the value of the 
clear_alarms 
key to 
1
, using the 
Raw Configure
option, to generate the clear alarm.
4.4
QOS_SQLSERVER_active_connection_ratio
Percent
Monitors the numbers of active connections.
4.4
QOS_SQLSERVER_active_users
Count
Monitors the number of users having an active transaction at the moment of snapshot.
4.4
QOS_SQLSERVER_alloc_space
Percent
Monitors allocated space.
4.4
QOS_SQLSERVER_av_fragmentation
Percent
Monitors average fragmentation.
4.4
QOS_SQLSERVER_average_waittime
ms
Monitors average lock wait time interval in ms. High wait time causes performance degradation, consider increase number of locks available or computer memory.
4.4
QOS_SQLSERVER_backup_status
Minutes
Monitors in minutes, since last database backup has been taken. For all databases that have never been backed up, this checkpoint returns -1 value.
4.4
QOS_SQLSERVER_blocked_users
Count
Monitors the number of blocked users.
4.4
QOS_SQLSERVER_buf_cachehit_ratio
Percent
Percentage of pages found in the buffer cache without having to read from the disk. The ratio is the interval number of cache hits divided by the interval number of cache look-ups.
Note
: As reading from the cache is less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to the SQL Server.
4.4
QOS_SQLSERVER_check_dbalive
State
Attempts to connect to the server. This checkpoint cannot be deactivated and returns two values with which threshold comparison is done:
  • Sql Server instance connection failure: 0
  • Sql Server instance connection success: 1
4.4
QOS_SQLSERVER_connection_memory
KB
Monitors amount of memory in KB that is used to maintain connections to SQL Server.
4.4
QOS_SQLSERVER_database_count
Count
Change in the number of databases on the server.
4.4
QOS_SQLSERVER_database_size
Megabytes
The size of the database.
4.4
QOS_SQLSERVER_database_state
State
State of the sql_server database. Each number is assigned a value, as follows:
  • 0: Online
  • 1: Restoring
  • 2: Recovering: SQL Server 2008 through SQL Server 2017
  • 3: Recovery pending: SQL Server 2008 through SQL Server 2017
  • 4: Suspect
  • 5: Emergency: SQL Server 2008 through SQL Server 2017
  • 6: Offline: SQL Server 2008 through SQL Server 2017
  • 7: Copying: Azure SQL Database Active Geo-Replication 
  • 10: Offline Secondary
4.4
QOS_SQLSERVER_deadlocks
Count/s
Monitors the number of deadlocks per second in an interval.
Note:
As deadlocks can cause severe performance penalty, count must be close to 0. Use trace 1204 or 1205 to identify the deadlocked resources and involved applications. Procedure such as sp_lock delivers useful information about locking.
4.4
QOS_SQLSERVER_differential_backup_status
Minutes
Monitors time in minutes since last differential backup.
4.4
QOS_SQLSERVER_fg_free_space
Percent
Monitors the amount of free space in database file groups in percent. If there is at least one file with "unlimited" growth in a file group, the space in this file group is considered as 100 percent free.
4.7
QOS_SQLSERVER_free_connections
Percent
Monitors percentage of free connections to SQL Server instance, specified by parameter 'user connections' ( the maximum value must be 32676).
4.4
QOS_SQLSERVER_free_space
Percent
Monitors the amount of free space in data files in percentage.
Note:
If there is at least one file with "unlimited" growth, the space in the whole database is considered as 100% free. If you are using file groups, this could be misleading; therefore, you must deactivate this checkpoint and use only the "fg_free_space" checkpoint.
4.4
QOS_SQLSERVER_full_scans
Count/sec.
Monitors the number of full table or index scans per second in interval. If this value is high (2-10), then you must analyze your queries.
4.4
QOS_SQLSERVER_latch_waits
Request/sec
Monitors the number of latch requests in an interval that could not be granted immediately and has to go in wait state.
Note:
If this number is high, the system experiences a low cache hit ratio and is forced to perform physical I/O operations. Add more memory or increase bandwidth of your system.
4.4
QOS_SQLSERVER_lock_memory
KB
Monitors amount of allocated lock memory in KB.
4.4
QOS_SQLSERVER_lock_requests
Requests/Sec
Monitors number of lock requests per second in interval.
4.4
QOS_SQLSERVER_lock_timeouts
Count/sec
Monitors number of lock-timeouts per second in interval with precision of 0.001sec
4.4
QOS_SQLSERVER_lock_waits
Count/sec
Monitors number of locks waits per second in interval.
4.4
QOS_SQLSERVER_locked_users
Count
Monitors the number of users suspended by locks at a given moment. Also, the blocked user and its current SQL are displayed.
4.4
QOS_SQLSERVER_locks_used
Percent
Monitors percentage of used lock and lock owner blocks.
4.4
QOS_SQLSERVER_log_cachehit_ratio
Percent
Monitors the percentage of pages found in the log cache without having to read from disk. The ratio is the interval number of cache hits divided by the interval number of cache look-ups.
Note
: Reading from the cache is much consumes less resources than reading from disk. You want this ratio to be high. You can increase the log cache hit ratio by increasing the amount of memory available to the SQL Server.
4.4
QOS_SQLSERVER_log_file_growths
Count
Monitors the number of times in an interval the transaction log for the database has been expanded. If this happens often, you must consider re-sizing your log files.
4.4
QOS_SQLSERVER_log_file_shrinks
Count
Monitors the number of times in an interval the transaction log for the database has been decreased. If this happens often, you must consider re-sizing your log files.
4.4
QOS_SQLSERVER_log_flush_waits
Count/sec.
Monitors the number of commits per second waiting on the log flush in an interval. When commits are waiting for log flushes, the log device is usually the bottleneck.
4.4
OQS_SQLSERVER_logfile_size
Count
Monitors the size of transaction log in MB for at least one transaction log file with "unlimited" growth in a database.
Note:
 For this checkpoint, wherever the given database is in the recovery or restore mode, no metric values are reported for given interval of execution.
4.4
QOS_SQLSERVER_logfile_usage
Percent
Monitors the amount of free space in transaction log in percentage. If there is at least one transaction log file with "unlimited" growth in a database, the space in transaction log is considered as 100 percent free.
Note:
 For this checkpoint, wherever the given database is in the recovery or restore mode, no metric values would be reported for given interval of execution.
4.4
QOS_SQLSERVER_logic_fragment
Percent
Monitors the number of cluster index pages that are out of order. Any number higher than 10% indicates external fragmentation. The index should be rebuilt.
Note:
 Non-cluster indexes are not monitored because a table can have only one clustering sequence.
4.4
QOS_SQLSERVER_login_count
Count
Monitors the number of users having an open connection to the server at a given time
4.4
QOS_SQLSERVER_long_queries
None
Monitors all queries running longer than defined threshold in seconds.
4.4
QOS_SQLSERVER_long_jobs
Count
Monitors all jobs running longer than defined threshold in seconds.
3.0
QOS_SQLSERVER_mirror_sqlinstance
State
Monitors availability of SQL server instance hosting the mirror database.
4.4
QOS_SQLSERVER_mirror_state
State
Monitors mirror database state.
4.4
QOS_SQLSERVER_mirror_witness_server
State
Monitors state of the witness server in the database mirror session.
4.4
QOS_SQLSERVER_optimizer_memory
Kilobyte
Monitors amount of memory in KB that is used for SQL optimizer.
4.4
QOS_SQLSERVER_page_reads
Count/sec.
Monitors the number of physical database page-reads that are issued per second in an interval.
Note:
Since physical I/O is expensive, you can minimize the cost, either by using a larger data cache, intelligent indexes, more efficient queries, or by changing the database design.
4.4
QOS_SQLSERVER_page_writes
Count/sec.
Monitors the number of databases page-writes that are issued per second in an interval.
Note:
Page-writes are generally expensive. Reducing page-write activity is important for optimal tuning. One way to do this is to ensure that you do not run out of free buffers in the free buffer pool. If you do, page-writes occurs while waiting for an unused cache buffer to flush.
4.4
QOS_SQLSERVER_scan_density
Ratio
Monitors the ratio between the best number of extents to the actual number of extents. It should be near 100 per cent. Lower number indicates external fragmentation and the object must be reorganized.
4.4
QOS_SQLSERVER_server_cpu
Percent
Monitors percentage of CPU usage by SQL Server instance in interval.
4.4
QOS_SQLSERVER_server_io
Percent
Monitors percentage of I/O busy for SQL Server instance in interval.
4.4
QOS_SQLSERVER_server_startup
Days
Number of days the database server is up and running.
4.4
QOS_SQLSERVER_sqlcache_memory
KB
Monitors amount of memory in KB that is used for SQL statement cache.
4.4
QOS_SQLSERVER_table_space
KB
Monitors amount of space (in KB/MB) reserved for a particular table in a database. This checkpoint can be used to control the size of fast growing tables.
4.4
QOS_SQLSERVER_total_memory
KB
Monitors total amount of dynamic memory (in KB) that the server uses currently.
4.4
QOS_SQLSERVER_transaction_backup_status
Minutes
Sends QoS and Alarms for those databases that are running in full or bulk-logged recovery mode.
Note
: This checkpoint does not send QoS and Alarms for databases that are running in simple recovery mode.
4.4
QOS_SQLSERVER_transactions
Transactions/sec
Monitors number of transactions per second in interval.
4.4
QOS_SQLSERVER_user_cpu
Percent
Monitors percentage of CPU usage by user in interval.
Note:
 The checkpoint 
user_cpu
 reports 
$spid.$hostid
 in the QoS target. This results in the creation of new data series for each new 
$spid
 or 
$hostid
. CA recommends disabling the QoS for this checkpoint.
4.4
QOS_SQLSERVER_workspace_memory
Percent
Monitors amount of memory in KB that is used for executing processes such as hash, sort, bulk copy, and index creation operations.
4.4
QOS_SQLServer_ls_primary_status
Status
Monitors collective status of agents for the primary log shipping database. This checkpoint must run from primary server or monitor server. The status can be as follows:
  • healthy and no-agent failures 1
  • otherwise 0
4.4
QOS_SQLServer_ls_time_since_last_backup
Minutes
Monitors time in minutes since last backup.
4.4
QOS_SQL_Server_ls_secondary_status
Status
Monitors collective status of agents for the secondary log shipping database. This checkpoint must run from secondary server or monitor server. The status can be as follows:
  • healthy and no-agent failures 1
  • otherwise 0
4.4
QOS_SQL_Server_ls_time_since_last_copy
Minutes
Monitors time in minutes since last copy.
4.4
QOS_SQL_Server_ls_time_since_last_restore
Minutes
Monitors time in minutes since last restore.
4.4
QOS_SQL_Server_ls_last_restored_latency
Minutes
Monitors time in minutes since last restored latency.
4.4
QOS_SQL_Server_fg_freeSpace_with_avail_disk
Percent
Monitors the amount of free disk space in database file groups in %. Free space for file groups (with auto growth enabled) is calculated after considering the available disk size on which the file group is located.
Notes:
  • A single query is executed for all the databases of the SQL server. If any of the database fails to execute the query, the query is considered as failed for the SQL server.
  • You require System Administrator privileges on the database server to execute this checkpoint.
4.4
QOS_SQL_Server_logfile_usage_with_avail_disk
Percent
Monitors free space in the database log files after considering the available disk size.
Note:
You require System Administrator privileges on the database server to execute this checkpoint.
4.7
QOS_SQL_Server_ls_primary_time_since_last_backup
Status
Monitors the length of time (in minutes), since the last log backup. If the value is NULL, it indicates that the information is not available or is not relevant. This checkpoint must run from primary server or monitor server.
4.4
QOS_SQL_Server_ls_secondary_last_restored_latency
Status
Monitors duration of time (in minutes) from the creation of the last backup to restore of the backup. If the value is NULL, it indicates that the information is not available or is not relevant. This checkpoint must run from secondary server or monitor server.
4.4
QOS_SQL_Server_ls_secondary_time_since_last_copy
Status
Monitors the length of time (in minutes), since the last log backup was copied. If the value is NULL, it indicates that the information is not available or is not relevant. This checkpoint must run from secondary server or monitor server.
4.4
QOS_SQL_Server_ls_secondary_time_since_last_restore
Status
Monitors the length of time (in minutes), since the last log backup was restored. If the value is NULL, it indicates that the information is not available or is not relevant. This checkpoint must run from secondary server or monitor server.
4.4
QOS_SQL_Server_suspect_pages
Gauge
Monitors suspect pages logged for databases.
4.4
QOS_SQL_Server_user_waits
Minutes
Monitors time in seconds for session spent waiting for a lock and length of blocking.
Note: 
You can add schedules in the
 Exclude
 and 
Include
 lists. The match expression, which is added will be executed in the given time period mentioned in the schedule.
4.8
QOS_SQLSERVER_aag_cluster_quorum_state
State
Monitors the quorum state of all AlwaysOn availability groups of Windows Server Failover Clustering (WSFC) cluster. Each number is assigned a value, as follows:
  • Unknown quorum state: 0
  • Normal quorum: 1
  • Forced quorum: 2
5.0
QOS_SQLSERVER_aag_cluster_members_state
State
Monitors the state of the nodes of all AlwaysOn availability groups of WSFC. Each number is assigned a value, as follows:
  • Offline: 0
  • Online: 1
5.0
QOS_SQLSERVER_aag_db_page_status
State
Monitors the page state of each database in all the AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Queued for request from partner: 2
  • Request sent to partner: 3
  • Queued for automatic page repair (response received from partner): 4
  • Automatic page repair succeeded and the page should be usable: 5
  • Irreparable: 6 (This indicates that an error occurred during page-repair attempt, for example, because the page is also corrupted on the partner, the partner is disconnected, or a network problem occurred. This state is not terminal; if corruption is encountered again on the page, the page will be requested again from the partner.)
5.0
QOS_SQLSERVER_aag_db_replica_synchronization_state
State
Monitors the synchronization state of each database replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Not synchronizing: 0
  • Synchronizing: 1
  • Synchronized: 2
  • Reverting: 3
  • Initializing: 4
From version 5.11, the probe generates alarms only if the synchronization state value is either 0, 3, or 4.
5.0
QOS_SQLSERVER_aag_listener_state
State
Monitors the listener state of all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Offline: 0
  • Online: 1
  • Pending restart: 2
  • Online: 3
5.0
QOS_SQLSERVER_aag_replica_connected_state
State
Monitors the connected state of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Disconnected: 0
  • Connected: 1
5.0
QOS_SQLSERVER_aag_replica_operational_state
State
Monitors the operational state of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Pending failover: 0
  • Pending: 1
  • Online: 2
  • Offline: 3
  • Failed: 4
  • Failed, no quorum: 5
  • Replica is not local: NULL
5.0
QOS_SQLSERVER_aag_replica_recovery_health
State
Monitors the recovery health of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Online_in_progress: 0
  • Online: 1
  • NULL
5.0
QOS_SQLSERVER_aag_replica_synchronization_health
State
Monitors the synchronization health of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Not healthy: 0 (At least one joined database is in the NOT SYNCHRONIZING state.)
  • Partially healthy: 1 (Some replicas are not in the target synchronization state: synchronous-commit replicas should be synchronized, and asynchronous-commit replicas should be synchronizing.)
  • Healthy: 2 (All replicas are in the target synchronization state: synchronous-commit replicas are synchronized, and asynchronous-commit replicas are synchronizing.)
5.0
QOS_SQLSERVER_aag_synchronization_health
State
Monitors the synchronization health of all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
  • Not healthy: 0 (None of the availability replicas have a healthy synchronization_health)
  • Partially healthy: 1 (The synchronization health of some, but not all, availability replicas is healthy.)
  • Healthy: 2 (The synchronization health of every availability replica is healthy.)
5.0
QOS_SQLSERVER_wait_stats_count
Count
Monitors the count of all the wait checkpoints, and displays the delta value of two intervals in the QoS. For example, if the current interval value is 20, and the previous interval value is 15, the delta value displayed is 5 (20-5). The alarm is generated if the delta value breaches the defined threshold.
5.0
QOS_SQLSERVER_wait_stats_time
ms
Monitors the total wait time in milliseconds for each wait checkpoint, and displays the delta value of two intervals in the QoS. For example, if the current interval value is 30 seconds, and the previous interval value is 20 seconds, the delta value displayed is 10 seconds (30-20). The alarm is generated if the delta value breaches the defined threshold.
5.0
Supported SQL Server Versions
The following table describes the checkpoint metrics, which are supported on SQL Server versions 2000, 2005, 2008, 2012, 2014, and 2016.
Checkpoint Metric
SQL Server 2012/SQL Server 2014/ SQL Server 2016
SQL Server 2005/SQL Server 2008
SQL Server 2000
active_connection_ratio
Yes
Yes
Yes
active_users
Yes
Yes
Yes
agent_job_failure
Yes
Yes
Yes
alloc_space
Yes
Yes
Yes
av_fragmentation
Yes
Yes
No
average_waittime
Yes
Yes
Yes
backup_status
Yes
Yes
Yes
blocked_users
Yes
Yes
Yes
buf_cachehit_ratio
Yes
Yes
Yes
check_dbalive
Yes
Yes
Yes
connection_memory
Yes
Yes
Yes
database_count
Yes
Yes
Yes
database_size
Yes
Yes
Yes
database_state
Yes
Yes
Yes
deadlocks
Yes
Yes
Yes
differential_backup_status
Yes
Yes
Yes
fg_free_space
Yes
Yes
Yes
free_connections
Yes
Yes
Yes
free_space
Yes
Yes
Yes
full_scans
Yes
Yes
Yes
latch_waits
Yes
Yes
Yes
lock_memory
Yes
Yes
Yes
lock_requests
Yes
Yes
Yes
lock_timeouts
Yes
Yes
Yes
lock_waits
Yes
Yes
Yes
locked_users
Yes
Yes
Yes
locks_used
Yes
Yes
Yes
log_cachehit_ratio
Yes
Yes
Yes
log_file_growths
Yes
Yes
Yes
log_file_shrinks
Yes
Yes
Yes
log_flush_waits
Yes
Yes
Yes
logfile_size
Yes
Yes
Yes
logfile_usage
Yes
Yes
Yes
logic_fragment
No
No
Yes
login_count
Yes
Yes
Yes
long_jobs
Yes
Yes
No
long_queries
Yes
Yes
No
mirror_sqlinstance
Yes
Yes
No
mirror_state
Yes
Yes
No
mirror_witness_server
Yes
Yes
No
optimizer_memory
Yes
Yes
Yes
page_reads
Yes
Yes
Yes
page_writes
Yes
Yes
Yes
scan_density
No
No
Yes
server_cpu
Yes
Yes
Yes
server_io
Yes
Yes
Yes
server_startup
Yes
Yes
Yes
suspect_pages
Yes
Yes
No
sqlcache_memory
Yes
Yes
Yes
table_space
Yes
Yes
Yes
total_memory
Yes
Yes
Yes
transaction_backup_status
Yes
Yes
Yes
transactions
Yes
Yes
Yes
user_cpu
Yes
Yes
Yes
user_waits
Yes
Yes
Yes
workspace_memory
Yes
Yes
Yes
ls_primary_status
Yes
Yes
No
ls_time_since_last_backup
Yes
Yes
No
ls_secondary_status
Yes
Yes
No
ls_time_since_last_copy
Yes
Yes
No
ls_time_since_last_restore
Yes
Yes
No
ls_last_restored_latency
Yes
Yes
No
fg_freeSpace_with_avail_disk
Yes
Yes
No
logfile_usage_with_avail_disk
Yes
Yes
Yes
aag_cluster_members_state
Yes
No
No
aag_cluster_quorum_state
Yes
No
No
aag_db_page_status
Yes
No
No
aag_db_replica_synchronization_state
Yes
No
No
aag_listener_state
Yes
No
No
aag_replica_connected_state
Yes
No
No
aag_replica_operational_state
Yes
No
No
aag_replica_recovery_health
Yes
No
No
aag_replica_synchronization_health
Yes
No
No
aag_synchronization_health
Yes
No
No
wait_stats_count
Yes
Yes
Yes
wait_stats_time
Yes
Yes
Yes
From April 2013, Microsoft has discontinued the support for SQL Server 2000 version. Therefore from SQL Server version 4.8, the enhancements in the sqlserver probe are not supported on the SQL Server version 2000.
Alert Metrics Default Settings
The following table describes the alert metrics default settings for the probe.
Alarm Metric
Warning Threshold
Warning Severity
Error Threshold
Error Severity
Description
Version
Active Connection Ratio
-
-
75
Major
Monitors ratio of active connections to total allowed connections.
4.4
Active Users
-
-
1
Information
This checkpoint monitors the number of users having an active transaction at the moment of snapshot.
4.4
Alloc Space
-
-
10
Major
Monitors free space in allocated data files regardless of auto-growth
4.4
Avg Fragmentation
-
-
25
Major
Monitors average fragmentation per allocation unit of an index or table.
4.4
Avg Wait Time
-
-
10
Information
Monitors average lock wait time in ms.
4.4
Backup Status
-
-
1440
Major
Monitors number of days since last backup.
4.4
Blocked Users
-
-
1
Information
Monitors the number of user blocked.
4.4
Cachehit Ratio
95
Warning
75
Major
Monitors the buffer cache-hit ratio
4.4
Availability
-
-
1
Major
Monitors connectivity to the database instance
4.4
Connection Memory
-
-
400
Information
Monitors amount of connection memory in KB.
4.4
Db Count
-
-
4
Information
Monitors the number of existing databases.
4.4
Db Size
-
-
1
Information
Monitors space size (in KB) for each database, log and data files together.
4.4
Db State
-
-
0
Major
Monitors database state
4.4
Deadlocks
-
-
0.01
Major
Monitors the number of deadlocks per second
4.4
Differential Backup Status
-
-
1440
Major
Monitors number of days since last differential backup
4.4
Fg Space
-
-
10
Major
Monitors free space in file groups
4.7
Free Connection
-
-
10
Major
Monitors % free connections to SQL Server instance.
4.4
Free Space
-
-
10
Major
Monitors free space in database.
4.4
Full Scans
-
-
0.1
Information
Monitors the number of full scans (table or index) per second
4.4
Latch Waits
-
-
0.01
Information
Monitors the number of latch requests per second
4.4
Lock Memory
-
-
400
Information
Monitors amount of allocated lock memory in KB
4.4
Lock Requests
-
-
0.1
Major
Monitors the number of lock requests per second
4.4
Lock Timeouts
-
-
0.01
Major
Monitor the number of lock-timeouts per second
4.4
Lock Waits
-
-
0.1
Major
Monitor the number of lock waits per second
4.4
Locked Users
-
-
1
Information
Monitors the number of users suspended by locks
4.4
Locks Used
-
-
80
Major
Monitors % of lock and lock owner blocks used.
4.4
Log Cachehit Ratio
-
-
95
Major
Monitors the log cache-hit ratio
4.4
Log File Growths
-
-
2
Information
Monitors the usage (growth) of the transaction logs
4.4
Log File Shrinks
-
-
2
Information
Monitors the usage (shrinking) of the transaction logs
4.4
Log Flush Waits
-
-
0.1
Information
Monitors the number of log flush waits per second
4.4
Log File Size
-
-
100
Major
Monitors log file size
4.4
Log File Usage
-
-
90
Major
Monitors free space in log files
4.4
Logic Fragment
-
-
25
Major
SQL Server 2000 only! Monitors logical fragmentation of an index or table.
4.4
Login Count
-
-
1
Information
Monitors the number of users currently logged onto the server
4.4
Long Jobs
-
-
10
Major
This checkpoint will find all jobs running longer then defined threshold in seconds
4.4
Long Queries
-
-
60
Major
Monitors long running queries (in seconds)
4.4
Optimizer Memory
-
-
200
Information
Monitors amount of optimizer memory in KB.
4.4
Page Reads
-
-
0.1
Information
Monitors the number of database page reads per second
4.4
Page Writes
-
-
0.5
information
Monitors the number of database page writes per second.
4.4
Scan Density
-
-
90
Major
SQL Server 2000 only! Monitors table/index fragmentation (density)
4.4
Server CPU
-
-
80
information
Monitors % of CPU usage by SQL Server instance
4.4
Server IO
-
-
80
Information
Monitors % of I/O busy for SQL Server instance.
4.4
Startup
-
-
120
Information
Monitors the uptime (in days) of the database server
4.4
Cache Memory
-
-
400
Information
Monitors amount of SQL cache memory in KB
4.4
Table Space
-
-
2097152
Information
Monitors reserved space in user tables.
4.4
Total Memory
-
-
15000
Information
Monitors total amount of dynamic server memory in KB.
4.4
Transaction Backup Status
-
-
1440
Major
Monitors number of days since last transaction log backup
4.4
Transactions
-
-
0.5
Major
Monitors the number of transactions per second
4.4
User CPU
-
-
50
Information
Monitors % of CPU usage by user.
4.4
User Waits
-
-
0.1
Information
Monitors time in seconds, session spends waiting for a lock.
4.4
Workspace Memory
-
-
80
Major
Monitors % of workspace memory allocated.
4.4
Profile Timeout
-
-
NA
Major
Defines the maximum processing time for all checkpoints in the profile. If this timeout is reached, the interval processing is finished and the probe waits for next heartbeat to evaluate any checkpoint schedules. Alarm message is issued.
4.4
SQL Error
-
-
NA
Major
SQL Native client error.
4.4
SQL Timeout
-
-
NA
Major
Every checkpoint query run asynchronously. In case the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started. Alarm is issued.
4.4
Query Checksum
-
-
NA
Major
Query manipulated.
4.4
Query Error
-
-
NA
Major
Returns data in unsupported format.
4.4
Suspect Pages
-
-
1
Major
Checks if suspect pages are logged for databases.
4.4
Agent Job Failure
-
-
15
Major
Monitors agent jobs which failed during the defined threshold interval (in minutes).
4.4
Primary Status
-
-
1
Major
Monitors collective status of agents for the primary log shipping database.
4.4
Secondary Status
 
 
1
Major
Monitors collective status of agents for the secondary log shipping database.
4.4
Primary Time Since Last Backup
-
-
60
Major
Monitors the duration(in minutes), since the last log backup was taken on primary database server in log shipping environment.
4.4
Secondary Time Since Last Copy
-
-
60
Major
Monitors the duration(in minutes), since the last log backup was copied on secondary database server in log shipping environment.
4.4
Secondary Time Since Last Restore
-
-
60
Major
Monitors the duration(in minutes), since the last log backup was restored on secondary database server in log shipping environment.
4.4
Secondary Last Restored Latency
-
-
60
Major
Monitors duration(in minutes) from the creation of the last backup to restore of the backup in log shipping environment.
4.4
Free Space with Available Disk
-
-
10
Major
Monitors free space in filegroups after considering the available disk size.
4.4
Log File Usage with Available Disk
-
-
25
Major
Monitors free space in the database log files after considering the available disk size.
4.7
AlwaysOn WSFC Nodes State
-
-
1
Major
Monitors the state of nodes of all AlwaysOn availability groups of WSFC.
5.0
AlwaysOn WSFC Quorum State
-
-
1
Major
Monitors the quorum state of all AlwaysOn availability groups of WSFC.
5.0
AlwaysOn Availability Database Page Status
-
-
6
Major
Monitors the page status of each database in all AlwaysOn availability groups of the server.
5.0
AlwaysOn Availability Database Replica Synchronization State
-
-
2
Major
Monitors the synchronization state of each database replica in all AlwaysOn availability groups of the server. 
5.0
AlwaysOn Availability Group Listener State
-
-
1
Major
Monitors the listener state of all AlwaysOn availability groups of the server.
5.0
AlwaysOn Availability Replica Connected State
-
-
1
Major
Monitors the connected state of a replica database in all AlwaysOn availability groups of the server.
5.0
AlwaysOn Availability Replica Operational State
-
-
2
Major
Monitors the operational state of a replica database in all AlwaysOn availability groups of the server. 
5.0
AlwaysOn Availability Replica Recovery Health
-
-
1
Major
Monitors the recovery health of a replica database in all AlwaysOn availability groups of the server.
5.0
AlwaysOn Availability Replica Synchronization Health
-
-
2
Major
Monitors the synchronization health of a replica database in all AlwaysOn availability groups of the server.
5.0
AlwaysOn Availability Synchronization Health
-
-
2
Major
Monitors the synchronization health of all AlwaysOn availability groups of the server.
5.0
Number of Waits Per Wait Type
-
-
1
information
Monitors the count of all the wait checkpoints.
5.0
Total Wait Time for Wait Type
-
-
1
information
Monitors the total wait time in milliseconds for each wait checkpoint.
5.0