3Click the Events > Timeline tabs and review the alerts, symptoms, and change events that
might help identify common trends that are contributing to the reported problem.
a To determine if other virtual machines had symptoms triggered and alerts generated at the
same time as your reported problem, click View From > Peer.
Other virtual machine alerts are added to the time line. If you see that multiple virtual
machines triggered symptoms in the same time frame, then you can investigate parent
objects.
b Click View From and select Host System from the Parent list.
The alerts and symptoms that are associated with the host on which the virtual machine
is deployed are added to the time line. Use the information to determine if a correlation
exists between the reported problem and the alerts on the host.
4Click the Events > Events tab to view changes in the collected metrics for the problematic
virtual machine. Metrics might direct you toward the cause of the reported problem.
a Manipulate the Date Controls to identify the approximate time when your customer
reported the problem.
b Use the Filters to filter on event criticality and status. Select Symptoms if you want to
include the filters in your analysis.
c Click an Event to view the details about the event.
d Click View From, select Host System under Parents, and repeat the analysis.
Comparing events on the virtual machine and the host, and evaluating those results, indicates
that CPU or memory problems are the likely cause of the problem.
5If the problem relates to CPU or memory use, click All Metrics and create metric charts to
identify whether it is CPU, memory, or both.
a If the host is still the focus, begin by working with host metrics.
b In the metric list, double-click the CPU Usage (%) and the Memory Usage (%) metrics to
add them to the workspace on the right.
c In the map, click the VPSALES4632 object.
The metric list now displays the virtual machine metrics.
d In the metric list, double-click the CPU Usage (%) and the Memory Usage (%) metrics to
add them to the workspace on the right.
e Review the host and virtual machine charts to see if you can identify a pattern that
indicates the cause of the reported problem.
Comparing the four charts shows normal CPU use on both the host and the virtual machine,
and normal memory use on the virtual machine. However, memory use on the host is
consistently elevated three days before the reported problem on VPSALES4632.
Using
VMware, Inc. 12