6.5.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- Monitoring Inventory Objects with Performance Charts
- Performance Chart Types
- Data Counters
- Metric Groups in vSphere
- Data Collection Intervals
- Data Collection Levels
- View Performance Charts
- Performance Charts Options Available Under the View Menu
- Overview Performance Charts
- Clusters
- Data centers
- Datastores and Datastore Clusters
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Datastores)
- Disk Space (Virtual Machines)
- Storage I/O Control Normalized Latency
- Storage I/O Control Aggregate IOPs
- Storage I/O Control Activity
- Average Device Latency per Host
- Maximum Queue Depth per Host
- Read IOPs per Host
- Write IOPs Per Host
- Average Read Latency per Virtual Machine Disk
- Average Write Latency per Virtual Machine Disk
- Read IOPs per Virtual Machine Disk
- Write IOPs Per Virtual Machine Disk
- Virtual Machine Observed Latency per Datastore
- Hosts
- Resource Pools
- vApps
- Virtual Machines
- CPU (%)
- CPU Usage (MHz)
- Disk (Average)
- Disk (Rate)
- Disk (Number)
- Virtual Disk Requests (Number)
- Virtual Disk Rate (KBps)
- Memory (Usage)
- Memory (Balloon)
- Memory (Swap Rate)
- Memory (Data Counters)
- Network (Usage)
- Network (Rate)
- Network (Packets)
- Disk Space (Data Counters)
- Disk Space (Datastores)
- Disk Space (File Types)
- Fault Tolerance Performance Counters
- Working with Advanced and Custom Charts
- Troubleshoot and Enhance Performance
- Monitoring Guest Operating System Performance
- Monitoring Host Health Status
- Monitoring Events, Alarms, and Automated Actions
- View Events
- View System Logs
- Export Events Data
- Streaming Events to a Remote Syslog Server
- Retention of Events in the vCenter Server Database
- View Triggered Alarms and Alarm Definitions
- Live Refresh of Recent Tasks and Alarms
- Set an Alarm
- Acknowledge Triggered Alarms
- Reset Triggered Event Alarms
- Preconfigured vSphere Alarms
- Monitoring Solutions with the vCenter Solutions Manager
- Monitoring the Health of Services and Nodes
- Performance Monitoring Utilities: resxtop and esxtop
- Using the vimtop Plug-In to Monitor the Resource Use of Services
- Monitoring Networked Devices with SNMP and vSphere
- Using SNMP Traps with vCenter Server
- Configure SNMP for ESXi
- SNMP Diagnostics
- Monitor Guest Operating Systems with SNMP
- VMware MIB Files
- SNMPv2 Diagnostic Counters
- System Log Files
- View System Log Entries
- View System Logs on an ESXi Host
- System Logs
- Export System Log Files
- ESXi Log Files
- Upload Logs Package to a VMware Service Request
- Configure Syslog on ESXi Hosts
- Configuring Logging Levels for the Guest Operating System
- Collecting Log Files
- Viewing Log Files with the Log Browser
- Enable the Log Browser Plug-In on the vCenter Server Appliance
- Enable the Log Browser Plug-In on a vCenter Server Instance That Runs on Windows
- Retrieve Logs
- Search Log Files
- Filter Log Files
- Create Advanced Log Filters
- Adjust Log Times
- Export Logs from the Log Browser
- Compare Log Files
- Manage Logs Using the Log Browser
- Browse Log Files from Different Objects
- Index
Table 1‑7. Data Counters
Chart Label Description
Usage Sum of the average CPU usage values, in Megaher, of all virtual machines in the cluster.
n
Counter: usagemhz
n
Stats Type: Rate
n
Unit: Megaher (MHz)
n
Rollup Type: Average (Minimum/Maximum)
n
Collection Level: 1 (4)
Total Total amount of CPU resources available in the cluster. The maximum value is equal to the
number of cores multiplied by the frequency of the processors.
For example, a cluster has two hosts, each of which has four CPUs that are 3GHz each, and one
virtual machine that has two virtual CPUs.
VM totalmhz = 2 vCPUs * 3000MHz = 6000MHz
Host totalmhz = 4 CPUs * 3000MHz = 12000MHz
Cluster totalmhz = 2 x 4 * 3000MHz = 24000MHz
n
Counter: totalmhz
n
Stats Type: Rate
n
Unit: Megaher (MHz)
n
Rollup Type: Summation
n
Collection Level: 1
Chart Analysis
A short spike in CPU usage indicates that you are making the best use of cluster resources. However, if the
value is constantly high, the CPU demanded is likely greater than the CPU capacity available. A high CPU
usage value can lead to increased ready time and processor queuing of the virtual machines on the hosts in
the cluster.
If performance is impacted, consider taking the following actions.
Table 1‑8. CPU Performance Enhancement Advice
# Resolution
1 Verify that VMware Tools is installed on each virtual machine.
2 If the cluster is not a DRS cluster, enable DRS. To enable DRS, perform the following tasks:
1 Select the cluster, and click the tab.
2 Under Services, click vSphere DRS.
3 click Edit.
An Edit Cluster Seings dialog box opens.
4 Click Turn ON vSphere DRS, and click OK.
3 If the cluster is a DRS cluster:
n
Increase the number of hosts, and migrate one or more virtual machines to the new host.
n
Check the aggressiveness threshold. If the value is low, increase the threshold. This might help avoid hot spots
in the cluster.
4 Migrate one or more virtual machines to a new host.
5 Upgrade the physical CPUs or cores on each host in the cluster if necessary.
6 Enable CPU-saving features, such as TCP Segmentation Ooad.
7 Replace software I/O with dedicated hardware, such as iSCSI HBAs or TCP Segmentation Ooad NICs.
vSphere Monitoring and Performance
14 VMware, Inc.