6.0.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- Updated Information
- 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
- Datacenters
- Datastores
- Disk Space (Data Counters)
- Disk Space (File Types)
- 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
- 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 Usage 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
- Index
Control When to Switch to New Virtual Machine Log Files
The vmx.log.rotateSize parameter specifies the log file size at which the switch to new log files happens for
the logs for individual virtual machines. Use this parameter together with the vmx.log.keepOld parameter to
ensure acceptable log file sizes without losing critical logging information.
The vmx.log.keepOld parameter determines how many virtual machine log file instances the ESXi host
retains before overwriting the first log file. The default value of vmx.log.keepOld is ten, a suitable number to
properly log complex operations such as VMotion. You must increase this number significantly when you
change the value of vmx.log.rotateSize.
This procedure discusses changing the virtual machine rotate size on an individual virtual machine.
To limit the rotate size for all virtual machines on a host, edit the /etc/vmware/config file. If the
vmx.log.KeepOld property is not defined in the file, you can add it. You can use a PowerCLI script to change
this parameter for selected virtual machines on a host.
You can use the log.rotateSize parameter to affect all log files, not just the virtual machine log files.
You can change the value of vmx.log.rotateSize for all virtual machine s from the vSphere Web Client or
by using a PowerCLI script.
Prerequisites
Turn off the virtual machine.
Procedure
1 Find the virtual machine in the vSphere Web Client inventory.
a Select a data center, folder, cluster, resource pool, or host.
b Click the Related Objects tab and click Virtual Machines.
2 Right-click the virtual machine and click Edit Settings.
3 Select VM Options.
4 Click Advanced and click Edit Configuration.
5 Add or edit the vmx.log.rotateSize parameter to the maximum file size before log information is
added to a new file, or to the first log file if you have more log files than the vmx.log.keepOld parameter
specifies.
Specify the size in bytes.
6 Click OK.
Collecting Log Files
VMware technical support might request several files to help resolve technical issues. The following sections
describe script processes for generating and collecting some of these files.
Set Verbose Logging
You can specify how verbose log files will be.
You can only set verbose logging for vpxd logs.
Procedure
1 Select Administration > vCenter Server Settings.
2 Select Logging Options.
vSphere Monitoring and Performance
168 VMware, Inc.