Generated alerts in vRealize Operations Manager appear in the alert lists. You use the alert lists to investigate, resolve, and begin troubleshooting problems in your environment.

In this scenario, you investigate and resolve the Virtual machine has unexpected high CPU workload alert. The alert might be generated for more than one virtual machine.

Process and take ownership of the alerts you will troubleshoot and resolve. See User Scenario: Monitor and Process Alerts in vRealize Operations Manager.

Review information about how the Power Off Allowed setting works when you run actions. See Working With Actions That Use Power Off Allowed.


In the left pane of vRealize Operations Manager, click the Alerts icon.


In the left pane, click the Health alert lists.


To limit the list to virtual machine alerts, click All Filters on the toolbar.


Select Object Type in the drop-down menu.


Enter virtual machine in the text box.


Click OK.

The alerts list displays only alerts based on virtual machines.


To locate the alerts by name, enter high CPU workload in the Quick filter (Name) text box.


In the list, click the Virtual machine has unexpected high CPU workload alert name.

The Alert Details Summary tab for the generated alert and affected object appears.


Review the Summary tab information.


Evaluation Process

Alert Description

Review the description so that you better understand the alert.


Do you think that implementing one or more of the recommendations will resolve the alert?

What is Causing the Issue?

Do the triggered symptoms support the recommendations? Do the other triggered symptoms contradict the recommendation, indicating that you must investigate further?

In this example, the triggered symptoms indicate that the virtual machine CPU demand is at a critical level and that the virtual machine anomaly is starting to get high.

Non-Triggered Symptoms

Some alerts are generated only when all the symptoms are triggered. Others are configured to generate an alert when any one of the symptoms are triggered. If you have non-triggered symptoms, evaluate them in the context of the triggered alerts.

Do the non-triggered symptoms support the recommendations? Do the non-triggered symptoms indicate that recommendations are not valid and that you must investigate further?


To resolve the alert based on the recommendation to check the guest applications to determine whether high CPU workload is an expected behavior, click the Action menu on the center pane toolbar and select Open Virtual Machine in vSphere Client.


Log in to the vCenter Server instance using your vSphere credentials.


Launch the console for the virtual machine and identify which guest applications are consuming CPU resources.


To resolve the alert based on the recommendation to add more CPU capacity to this virtual machine, click Set CPU Count for VM.


Enter a new value in the New CPU text box.

The value that appears is the calculated recommended size. If vRealize Operations Manager was monitoring the virtual machine for six or more hours, depending on your environment, the value that appears is the CPU Recommended Size metric.


Select the following options to allow power off or to create a snapshot, depending on how your virtual machines are configured.



Power Off Allowed

Shuts down or powers off the virtual machine before modifying the value. If VMware Tools is installed and running, the virtual machine is shut down. If VMware Tools is not installed or not running, the virtual machine is powered off without regard for the state of the operating system.

In addition to whether the action shuts down or powers off a virtual machine, you must consider whether the object is powered on and what settings are applied.


Creates a snapshot of the virtual machine before you add CPUs.

If the CPU is changed with CPU Hot Plug enabled, then the snapshot is taken with the virtual machine running, which consumes more disk space.


Click OK.

The action adds the recommended number of CPUs to the target virtual machine.


Allow several collection cycles to run after implementing the recommended changes and check the alert list.

If the alert does not reappear after several collection cycles, it is resolved. If it reappears, further troubleshooting is required. For an alternative scenario for troubleshooting alerts, see User Scenario: An Alert Arrives in Your Inbox.