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 alerts can provide visual clues to the root cause of a problem.

As a virtual infrastructure administrator investigating a reported performance problem with a virtual machine, you compared symptoms on the timeline. You identified odd behavior related to a guest file system that you want to examine in the context of other metrics. This investigation can determine whether you 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.

Prerequisites

Examine triggered symptoms, alerts, and events over time. See Compare Symptoms on a Timeline When You Troubleshoot a Virtual Machine Problem.

Procedure

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

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

  2. Click the Events tab and select the Events button.
  3. On the Events toolbar, click Date Controls and select a time that is on or before the symptoms were triggered.
  4. Click Event Filters and select all the event types.

    Consider whether any changes correspond to other events.

  5. Click View From > Parent > Select All and click through the alerts in the timeline to review 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.

  6. Click View From > Child > Select All and click through the alerts to review the events.

    Consider whether any of the events show problems with the datastore.

Results

Your evaluation shows no particular correlation between the workload and the time at which the guest file system out-of-space symptom was triggered each time.