Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN 8.1 Administrator Guide > Use the Virtual Infrastructure Monitor > Configure virtualization thresholds > Edit a VM specific threshold

Edit a VM specific threshold

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Dec 04, 2017

Views: 10 Votes: 0 Revisions: 3

Updated: November 30, 2017

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.

    File:Success_Center/Reusable_content_-_InfoDev/VMAN/VMAN_8.1_Admin_Guide/0020-Optimizing_virtual_resources/0060-Customize_and_configure_VMAN/0020-Configure_virtualization_thresholds/0050-How_thresholds_affect_recommendations/virtualization-thresholds.png

  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.

    File:Success_Center/Reusable_content_-_InfoDev/VMAN/VMAN_8.1_Admin_Guide/0020-Optimizing_virtual_resources/0060-Customize_and_configure_VMAN/0020-Configure_virtualization_thresholds/0030-Edit_a_VM_specific_threshold/vm-thresholds-edit_765x247.png

  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.

    File:Success_Center/Reusable_content_-_InfoDev/VMAN/VMAN_8.1_Admin_Guide/0020-Optimizing_virtual_resources/0060-Customize_and_configure_VMAN/0020-Configure_virtualization_thresholds/0030-Edit_a_VM_specific_threshold/vm-thresholds-baselines.png

    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

Tags

Classifications

Public