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 7‑4. CPU Panel Statistics (Continued)
Line Description
%RDY Percentage of time the resource pool, virtual machine, or world was ready to run, but was not
provided CPU resources on which to execute.
100% = %RUN + %RDY + %CSTP + %WAIT
%MLMTD (max
limited)
Percentage of time the ESXi VMkernel deliberately did not run the resource pool, virtual machine,
or world because doing so would violate the resource pool, virtual machine, or world's limit
seing. Because the resource pool, virtual machine, or world is ready to run when it is prevented
from running in this way, the %MLMTD (max limited) time is included in %RDY time.
%SWPWT Percentage of time a resource pool or world spends waiting for the ESXi VMkernel to swap
memory. The %SWPWT (swap wait) time is included in the %WAIT time.
EVENT COUNTS/s Set of CPU statistics made up of per second event rates. These statistics are for VMware internal
use only.
CPU ALLOC Set of CPU statistics made up of the following CPU allocation conguration parameters.
AMIN Resource pool, virtual machine, or world aribute Reservation.
AMAX Resource pool, virtual machine, or world aribute Limit. A value of -1 means unlimited.
ASHRS Resource pool, virtual machine, or world aribute Shares.
SUMMARY STATS Set of CPU statistics made up of the following CPU conguration parameters and statistics. These
statistics apply only to worlds and not to virtual machines or resource pools.
AFFINITY BIT
MASK
Bit mask showing the current scheduling anity for the world.
HTSHARING Current hyperthreading conguration.
CPU
The physical or logical processor on which the world was running when resxtop (or esxtop)
obtained this information.
HTQ Indicates whether the world is quarantined or not. N means no and Y means yes.
TIMER/s Timer rate for this world.
%OVRLP Percentage of system time spent during scheduling of a resource pool, virtual machine, or world
on behalf of a dierent resource pool, virtual machine, or world while the resource pool, virtual
machine, or world was scheduled. This time is not included in %SYS. For example, if virtual
machine A is being scheduled and a network packet for virtual machine B is processed by the
ESXi VMkernel, the time spent appears as %OVRLP for virtual machine A and %SYS for virtual
machine B.
%USED = %RUN + %SYS - %OVRLP
%RUN Percentage of total time scheduled. This time does not account for hyperthreading and system
time. On a hyperthreading enabled server, the %RUN can be twice as large as %USED.
%USED = %RUN + %SYS - %OVRLP
100% = %RUN + %RDY + %CSTP + %WAIT
%CSTP Percentage of time a resource pool spends in a ready, co-deschedule state.
N You might see this statistic displayed, but it is intended for VMware use only.
100% = %RUN + %RDY + %CSTP + %WAIT
POWER Current CPU power consumption for a resource pool (in Was).
%LAT_C Percentage of time the resource pool or world was ready to run but was not scheduled to run
because of CPU resource contention.
%LAT_M Percentage of time the resource pool or world was ready to run but was not scheduled to run
because of memory resource contention.
vSphere Monitoring and Performance
134 VMware, Inc.