Events are changes to objects in your environment that are based on changes to metrics, properties, or information about the object. Examining the events for the problematic virtual machine in the context of the analysis badges and alerts might provide visual clues to the root cause of a problem.
About this task
As a virtual infrastructure administrator investigating a reported performance problem with a virtual machine, you compared symptoms on the timeline and identified interesting behavior around the guest file system that you want to examine in the context of other badge metrics to determine if you can find the root cause of the problem.
The following method of evaluating problems using the Events 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.
Examine triggered symptoms, alerts, and events over time. See Compare Symptoms on a Timeline When You Troubleshoot a Virtual Machine Problem
- 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 Events tab.
- On the Events toolbar, click Date Control and select a time that is on or before the symptoms were triggered.
- Click Select Event Type and select all of the event types.
Consider whether any changes correspond to other events.
- Click Show Parent Events and click through the badges on the toolbar to review the events.
Consider whether any of the events, which are listed in the data grid below the chart, correspond to problems with the host that might contribute to the reported problem.
- Click Show Child Events and click through the badges on the toolbar to review the events.
Consider whether any of the events show problems with the datastore.
Your evaluation shows no particular correlation between the workload or anomalies and the time at which the guest file system out of space symptom was triggered each time.