Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Storage Resource Monitor (SRM) > SRM Documentation > Storage Resource Monitor (SRM) Getting Started Guide > Thresholds > How thresholds work in SRM

How thresholds work in SRM

Table of contents
No headers
Created by Anthony.Rinaldi_ret, last modified by Melanie Boyd on Nov 21, 2016

Views: 155 Votes: 0 Revisions: 3

Thresholds are the values assigned to metrics of a monitored device or device type to indicate the levels at which the device require attention. You can set Critical and Warning status thresholds for each metric for each object type (or individual objects).

In the following example, the Latency (Total) threshold for LUNs is set to 20 milliseconds or higher for Critical, and 10 to 19 milliseconds for Warning.

The resource on the right shows three LUNs and their current latency:

  • The first LUN exceeds the Critical level threshold, so Latency is shown against a red background, and the resource name is preceded by the Critical icon.
  • The second LUN exceeds the Warning level but not the critical level so is shown against a yellow background, and the resource name is preceded by the Warning icon.
  • The third LUN is below the Warning level so it is not highlighted, and the resource name is preceded by the Up icon.


Last modified