Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Storage Resource Monitor (SRM) > SRM Documentation > SRM 6.7 Administrator Guide > Manage thresholds for SRM

Manage thresholds for SRM

Table of contents
No headers
Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 91 Votes: 0 Revisions: 1

Orion Platform products provide two threshold levels: critical and warning. Many SRM resources can display a critical or warning status when a monitored value on a device exceeds thresholds. You can override all storage objects of the same type (for example, all storage arrays in your monitored environment) or for individual objects for predefined static thresholds.

Thresholds can be used to define trigger conditions when creating alerts.

To change the value for a threshold, you can use a static threshold or a dynamic baseline threshold.

  • A static threshold is a constant value. For example, the global warning threshold for LUN latency might be 50 ms, and the critical value might be 100 ms. You should be familiar with the performance of that object type or specific object to set a value for a static threshold is across your environment.
  • A dynamic baseline threshold uses deviation from the mean value to determine critical and warning thresholds. Dynamic baseline thresholds can only be set for individual objects.

    Dynamic thresholds require data to be collected for a week for an accurate baseline to be determined. This is then used to calculate mean and standard deviations. The warning and critical threshold values are defined as two or three standard deviations above the mean.

Last modified