6.7
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)
- Space Allocated by Datastore in GB
- Space Capacity by Datastore in GB
- 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 vSphere Health
- 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 in the vSphere Web Client
- Set an Alarm in the vSphere Client
- 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
Table 1‑13. Data Counters
Chart Label Description
Consumed Amount of host machine memory used by all powered on virtual machines in the cluster. A cluster's
consumed memory consists of virtual machine consumed memory and overhead memory. It does not
include host-specific overhead memory, such as memory used by the service console or VMkernel.
n
Counter: consumed
n
Stats Type: Absolute
n
Unit: Megabytes (MB)
n
Rollup Type: Average (Minimum/Maximum)
n
Collection Level: 1 (4)
Total Total amount of machine memory of all hosts in the cluster that is available for virtual machine memory
(physical memory for use by the Guest OS) and virtual machine overhead memory.
Memory Total = Aggregate host machine memory - (VMkernel memory + Service Console memory +
other service memory)
Note The totalmb data counter is the same as the effectivemem data counter, which is supported only
for backward compatibility.
n
Counter: totalmb
n
Stats Type: Absolute
n
Unit: Megabytes (MB)
n
Rollup Type: Average (Minimum/Maximum)
n
Collection Level: 1 (4)
Chart Analysis
Memory usage is not an indicator of performance problems. Memory can be high if a host is swapping or
ballooning, which can result in virtual machine guest swapping. In such cases, check for other problems,
such as CPU over-commitment or storage latencies.
If you have constantly high memory usage in a cluster, resource pool, or vApp, consider taking the
following actions.
Table 1‑14. Memory Performance Enhancement Advice
# Resolution
1 Verify that VMware Tools is installed on each virtual machine.
2 Verify that the balloon driver is enabled. The balloon driver is installed with VMware Tools and is critical to performance. The
VMkernel regularly reclaims unused virtual machine memory by ballooning and swapping. Generally, it does not impact virtual
machine performance.
3 If the balloon value is high, check the resource shares, reservations, and limits for the virtual machines and resource pools on
the hosts. Verify that the host's settings are adequate and not lower than those set for the virtual machine. If free memory is
available on the hosts and the virtual machines are experiencing high swap or balloon memory, the virtual machine (or
resource pool, if it belongs to one) has reached its resource limit. Check the maximum resource limit set on that host.
vSphere Monitoring and Performance
VMware, Inc. 19