As you respond to customer complaints and alerts, or when you notice problems in your environment, the information provided on the Symptoms tab in vRealize Operations Manager helps you determine if the triggered symptoms indicate conditions that contribute to the reported or identified problem.

As a network operations engineer, you are doing more research regarding a virtual machine about which one of your customer reports poor performance. When you view the Alerts tab for the virtual machine, you see only the Virtual Machine is Violating vSphere 5.5 Hardening Guide alert.

You identified problems with memory and disk space when you reviewed the Analysis tabs, so you focus your review of the triggered symptoms on those items.

The following method of evaluating problems using the Symptoms tab is provided as an example for using vRealize Operations Manager and is not definitive. Your troubleshooting skills and your knowledge of the particulars of your environment determine which methods work for you.


Enter the name of the virtual machine in the Search text box, located on the main title bar.

In this example, the virtual machine name is sales-10-dk.


Click the Troubleshooting tab and click the Symptoms tab.


Review the triggered symptoms.


Evaluation Process


Are any of the triggered symptoms related to the critical states you see for memory or disk space?


Are the symptoms active or inactive? Even inactive symptoms can provide information about the past state of the object. To add the inactive symptoms, click Status: Active on the toolbar to remove the filter.

Create On

When was the symptoms triggered? How does the time that they were triggered compare with other symptoms?


Can you identify a correlation between the triggered symptoms and the state of the Time Remaining and Capacity Remaining badges?

From your review of the symptoms you determine that most of the triggered symptoms are associated with the Virtual Machine Hardening Guide alert, but some of the symptoms appear to be for memory and time remaining, including the following symptoms:

Guest file system overall disk space usage reaching critical limit

Virtual machine disk space time remaining is low

Virtual machine CPU time remaining is low

Guest partition disk space usage

Virtual machine memory time remaining is low