Use the VM Performance dashboard to find out if a VM has a performance problem. As a first step, when a VM has a problem, verify if other VMs have the same problem. If the problem is widespread the root cause is not with the VM.
How to Use the Dashboard
The VM Performance dashboard is organized into sections for ease of use.
- Select a data center from the Datacenters widget. To find out if there is a performance problem, what the problem is, and the extent of the problem, use the following three bar charts together: Are VMs facing CPU Ready, Are VMs facing Memory Contention, Are VMs facing Disk Latency. Each bar chart analyzes how the VMs are served by the cluster. These bar charts indicate if the VMs are waiting for CPU resources, facing memory contention, or disk latency. For each VM, it picks the worst metric in the last 24 hours. By default, vRealize Operations collects data every 5 minutes, so this is the highest value among 288 datapoints (12 x 24 = 288). Once it has the value from each VM, the bar charts put each VM in the respective performance buckets. The threshold in the buckets considers best practices, and hence they are color coded. For each bar chart, you can change the time period to the period of your interest. The maximum number is then displayed. The value is the worst 20-seconds, within the 5-minute collection time period. For your mission-critical environment, you must expect that all the VMs are being served well by the IaaS. If you see green on the distribution charts, you do not have to analyze further.
For development, you may tolerate a small amount of contention in both CPU and Memory as you need to balance cost.
You can also change the filter from data center to cluster. If you are listing clusters, you can then add the cluster performance (%) metric and sort them in ascending order. This way the cluster that needs immediate attention is on top.
You can click on the bar to see the list of VMs under that performance bucket. From there, you can select a VM, and it's KPI is automatically displayed on the lower section of the dashboard.
See AlsoMonitor IOPS in VMware vSphere - Multiple VM Analysis
When you select a data center from the VMs Performance in selected Datacenter widget, the table listing all the VMs in the data center is displayed.
The table is sorted by the KPI Breached column, directing your attention to the VMs that are not served well by the IaaS. The column counts the number of SLA breaches in any given 5-minute period. It is based on the counter
Performance \ Number of KPIs Breached. As a VM consumes four resources of IaaS (CPU, memory, disk, and network), the counter varies from zero through four, with zero being the ideal. The value four indicates that all four IaaS services are not delivered. The same threshold is used regardless of class of service, as this is an internal KPI, and not an external SLA.Because the goal is proactive monitoring, as opposed to reactive troubleshooting, the counters show the worst value instead of the average of the monitoring period.
- Per VM Analysis
When you select a VM from the table, the CPU, memory, disk, and network performance charts are automatically displayed, each widget showing the KPIs of that VM.
- Alerts
The relevant alerts are displayed automatically. You can view the settings by editing the widget, and adjust them accordingly to fit your operational needs.
- Virtual Disks
A VM can have many disks, and it is possible that these disks may have different performance levels. The table lists the individual virtual disks and their contention and utilization metrics.
- Configuration
The relevant configuration of the selected VM is displayed. You can customize as appropriate.
- Relationship
From the VM, you can navigate to the parent cluster or datastore. Use the Relationship widget to navigate and auto select the associated cluster or datastore.
