Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.





Home > Success Center > Virtualization Manager (VMAN) > VMAN Getting Started Guide > Customize thresholds > How thresholds work

How thresholds work

Table of contents
No headers
Created by Lori Krell, last modified by Melanie Boyd on Nov 22, 2016

Views: 288 Votes: 0 Revisions: 2

Alerts and recommendations are triggered when a monitored value exceeds a threshold. Thresholds set the trigger levels for warning and critical alerts and recommendations. Thresholds include global Orion Platform thresholds, global virtualization thresholds, and specific VM thresholds. As the Orion Web Console collects and calculates data for VM performance, resource consumption, and status, all thresholds are compared against the data to pinpoint active and potential issues.

Thresholds include:

  • Orion Platform thresholds - The Orion Platform comes with predefined static thresholds for Orion product modules at the node level including average CPU load, disk usage, percent memory used, percent packet loss, and response time.

    For more information, see the SolarWinds Virtualization Manager Administrator Guide.

  • Virtualization Manager thresholds - VMAN uses a set of virtualization thresholds for triggering virtual system specific alerts and recommendations. These thresholds include network utilization, CPU load, memory usage, IOPS, latency, and capacity. You can configure these thresholds globally or override per cluster, host, datastore, or VM.

    Specific thresholds support only CPU load, memory usage, and network utilization.

If you want to change the predefined value for a threshold, you use a static threshold or a dynamic baseline threshold.

Static threshold

This threshold is a constant value that you set for your threshold. The value does not change unless edited.

Example: You may enter a static value for the response time threshold as warning 500 ms and critical as 1000 ms.

Dynamic baseline threshold

Data for a threshold is collected for a week and used to calculate mean and standard deviation. The warning and critical threshold values are defined as 2 and 3 standard deviations above the mean, respectively. Dynamic baseline thresholds are the most accurate way to define thresholds for a specific device. You can recalculate baselines on demand after making threshold changes.

Example: If the mean value for packet loss for a specific node is 0%, the warning threshold for packet loss would be 3% (+2 standard deviations) and the critical threshold would be 4% (+3 standard deviations).

Learn more...

To manage thresholds:

Last modified
18:26, 21 Nov 2016