To troubleshoot problems with the VPSALES4632 virtual machine, you evaluate the symptoms, examine time line information, consider events, and create metric charts to find the root cause of the problem.

If a review of the alerts did not help you identify the cause of the problem reported for the virtual machine, use the Troubleshooting tabs, Symptoms, Timeline, Events, and All Metrics, to troubleshoot the history and current state of the virtual machine.

Locate the object for which the problem was reported. See Search for a Specific Object.

Review the alerts for the virtual machine to determine if the problem is already identified and recommendations made. See Review Alerts Related to Reported Problems.

1

If you are viewing the Alert Details tabs, click Virtual Machine in the left pane and select VPSALES4632 in the lower list.

The main pane updates to the display the object Summary tab.

2

Click the Troubleshooting tab, click the Symptoms tab, and review the symptoms to determine if one of the symptoms is related to the reported problem.

Depending on how your alerts are configured, some symptoms might be triggered but not sufficient to generate an alert.

a

Review symptom names to determine if one or more symptoms are related to the reported problem.

The Information column provides the triggering condition, trend, and current value. What are the most common symptoms that affect response time? Do you see any symptoms related to CPU or memory usage?

b

Sort by the Created On date so that you can focus on the time frame in which your customer reported that the problem.

c

Click the Status: Active filter button to disable the filter so that you can review active and inactive symptoms.

Based on symptoms, you think the problem is related to CPU or memory use. But you do not know if the problem is with the virtual machine or with the host.

3

Click the Timeline tab and review the alerts, symptoms, and change events over time that might help you 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 Show Peer Events.

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 ancestor objects.

b

Click the Show Ancestor Events and select Host System.

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.

4

Click the Events tab to view changes in the collected metrics for the problematic virtual machine that could direct you toward the cause of the reported problem.

a

Use the Date Controls option view event for the approximate time when your customer reported the problem.

b

Click through the Workload, Capacity, and Stress badges to determine if any events are associated with the problem.

c

Click Zoom the View and zoom in on any events or event clusters that occurred at or before the problem was reported.

d

Click Show Data Values and place the cursor over an event to view the details about the event.

The events for the selected time also appear in the data grid below the event chart.

e

In the left pane, click Host System, click the host name in the list on the lower left pane, and repeat the analysis of the host using Workload, Capacity, and Stress.

Comparing events on the virtual machine and the host, and evaluating those results, indicates that CPU or memory issues are the likely cause of the problem.

5

If you can identify that the problem is related to, for example, CPU or memory use, click the All Metrics tab to create your own metric charts so that you can determine whether it is one or the other, or a combination.

a

If host is still the focus, then start 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.

In this scenario, comparing the four charts reveals that CPU use is normal on both the host and the virtual machine, and the memory use is normal on the virtual machine. However, the memory use on the host began going consistently high three days before the reported problem on the VPSALES4632 virtual machine.

The host memory is running consistently high, affecting the response time for the virtual machines. The number of virtual machines it is running is well within the supported amounts. The possible cause might be too many high process applications on the virtual machines. You can move some of the virtual machines to other hosts, distribute the workload, or power off idle virtual machines.

In this example, you can use vRealize Operations Manager to power off virtual machines on the host so that you can improve the performance of the virtual machines that are in use. See Run Actions From Toolbars in vRealize Operations Manager.

If the combination of charts that you created on the All Metrics tab are something that you might want to use again, click Generate Dashboard.

If you did not resolve the problem, continue your investigation.