Virtual Machine(s) Workload badge reports constant 100+ score in VMware vRealize Operations Manager
search cancel

Virtual Machine(s) Workload badge reports constant 100+ score in VMware vRealize Operations Manager

book

Article ID: 328773

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • In vRealize Operations Manager, you see these symptoms:
     
    • Virtual Machine Workload badge reports a constant 100+ score.
    • CPU|Workload badge reports a constant 100+ score.
    • CPU|Demand (%) metric reports constant 100+ values.
       
  • In vSphere Web Client, Virtual Machine(s) display low CPU usage and no contention.


Environment

VMware vRealize Operations Manager 6.7.x
VMware vRealize Operations 8.x
VMware vRealize Operations Manager 7.5.x
VMware vRealize Operations Manager 6.6.x
VMware vRealize Operations Manager 7.0.x

Cause

In most cases, this issue occurs when Virtual Machines have the Latency-Sensitivity Feature enabled (set to HIGH) which keeps the CPU demand value at 100%.
vRealize Operations Manager cannot determine if Virtual Machines are Latency Sensitive. This causes CPU contention Alerts and/or Memory Contention Alerts as vRealize Operations Manager cannot determine the 100% CPU reservation requested by the Virtual Machine.
 
Note: CPU|Workload is based on CPU demand. CPU demand is the amount of CPU resources a virtual machine would use if there were no CPU contention or CPU limit.

Resolution

This is expected behavior in vRealize Operations Manager.
 


Workaround:
To Workaround this behavior, disable the Latency-Sensitivity feature setting for the Virtual Machine(s) in the vSphere Web client.
  1. Log in to vSphere Web client.
  2. Select the Virtual Machine.
  3. Click Edit Settings.
  4. Click VM options > Advanced.
  5. Set Latency Sensitivity option to Normal.

Alternatively, choose to ignore the alerts, or create a Policy applied to a Custom Group to disable the alerts in vRealize Operations Manager.
To create a Policy applied to a Custom Group, follow the steps below.
  1. Log into vRealize Operations Manager as an Administrative user.
  2. Navigate to Environment > Custom Groups.
  3. Click New Custom Group.
  4. Enter a Name, select a Group Type, and define membership criteria or manually choose objects to include and/or exclude.
Note: Define and/or include objects that you want to disable alerts on.
  1. Click OK.
  2. Navigate to Administration > Policies > Policy Library.
  3. Click Add New Policy.
  4. Enter a Name.
  5. In the Start with field, choose a policy your want to clone.
  6. Select section 6. Alert / Symptom Definitions.
  7. In the Alert Definitions pane, change the State to Disabled Local for Alerts that you want to disable.
  8. In the Symptom Definitions pane, change the State to Disabled Local for Symptoms that you want to disable.
  9. Select section 7. Apply Policy to Groups.
  10. Check the Custom Group created in step 4.
  11. Click Save.


Additional Information

 


Powered by Wolken Software