Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Virtualization Manager (VMAN) > Virtualization Manager (VMAN) Getting Started Guide > Customize thresholds > Edit a VM specific threshold

Edit a VM specific threshold

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

Views: 26 Votes: 0 Revisions: 3

As recommendations and alerts trigger, the default global thresholds may need to be adjusted for the baselines of your environment. In some cases, alerts may constantly trigger or cause false positives depending on factors including the amount of network traffic, capacity usage, and intended use of the cluster, host, datastore, or VM.

For this example, the CPU load for Microsoft Exchange VM servers can greatly differ than the load by normal application and storage VMs. The default thresholds for CPU load may trigger false positive alerts for the Exchange servers. To better monitor and generate alerts, create specific VM thresholds for the Exchange servers using Dynamic Baselines.

  1. Click Settings > All Settings.
  2. In the Product Specific Settings section, click Virtualization Settings.
  3. In the Virtualization Settings section, click Virtualization Thresholds.

    The Virtualization Thresholds page displays with a list of VMs.


  4. Locate and select the checkboxes your Microsoft Exchange VMs, and click Edit Thresholds.

    An Edit Properties page displays with thresholds to override and edit.

  5. For the CPU load and Memory Usage, click Override Global Orion Threshold or Set Dynamic Threshold.

    For this example, Microsoft Exchange VMs undergoes consistent, heavy CPU load, memory usage, and capacity usage. Setting a specific warning or critical amount could still generate false positives. Due to the constant fluctuation, using dynamic baselines allows the system to calculate the correct baselines based on actual tracked usage and metrics for the VM.


  6. Click Latest Baseline Details to review the latest metrics tracked for the VM. The following example gives you insight to how the baselines are generated. Metric over Time tracks the full bandwidth of CPU load, indicating the actual average CPU usage. A spike in usage as noted in the tooltip shows the above average usage compared to the baseline.

    VMAN creates a baseline of normal, warning level, and critical level of CPU usage directly from this captured data.


    Click Cancel to close.

  7. Click Use Dynamic Baseline Thresholds.

    This option calculates and sets baselines based on monitored metrics over time for the Exchange servers, providing more accurate alerting and recommendations.

  8. Click Submit.

Learn more...

To manage thresholds:

Last modified
18:27, 21 Nov 2016