This metric returns the longest running instance of the named job in the last hour. By creating multiple custom metrics from this example – one for each job you're interested in – you can specify alert thresholds for each job individually. Read more
This metric measures the total number of indexes per database, where the number of writes exceed the number of reads. It provides a general indicator of possible performance factors affecting queries in your database. Read more
A high plan cache hit ratio does not guarantee that all queries are using the cache as well as they might. Knowing the percentage of queries that are satisfied from cache helps you to better understand the plan cache hit ratio value. Read more
This metric shows the percentage of cached plans that are being used more than once. If a plan is cached but never reused, there may be an opportunity to tune your server to work more effectively. Read more
This metric gives an idea of how many task are in a runnable state and trying to execute in the system concurrently. Read more
What are custom metrics?
The SQL Monitor custom metric feature lets you run T-SQL queries against your SQL Servers to collect specific data. You can analyze and receive alerts about your custom data just like everything else SQL Monitor collects.
But what if you don’t want to write your own queries? No problem. Redgate has brought together a range of quality custom metrics for you to use in SQL Monitor, which are all are free, tried and tested. You can install straight away, and use the resources on this site to help you write your own.
This custom metric measures the total database file size (data files and log file combined). An increase in this metric signals that a database was grown. When not done by the DBA, this is an autogrow. Excessive autogrow events should be prevented as this can result to file fragmentation. Try to manually grow files before […] Read more
This metric will display the total number of active backups and restores on a server. This can be used to correlate with other metrics to explain why disk IO and CPU usage could have changed. Read more