Collecting an ESX Performance Snapshot

The logs that you collect from the vCenter and ESX host do not include performance statistics/snapshots. But you can use the information in this section to collect performance snapshots. This information is also available in the VMware Knowledge Base (http://kb.vmware.com/kb/1967).

 

Note icon Note: If you collect performance statistics logs, you need to have an ESX host to read them.

 

Performance snapshots are continuous snapshots of proc nodes, collected at defined intervals for a specified period. VMware Technical support may ask customers to send performance snapshots to help troubleshoot a performance issue in response to a service request that a customer opened.

 

To collect the performance snapshots:

 

  1. Log in to your ESX host with root privileges, using the console or an SSH session.

     

  2. Run this command:

•  ESX/ESXi 4.1 and earlier releases: vm-support -s 

•  ESXi 5.0: vm-support -p 

 

    You may specify the collection duration and interval in seconds, using these command-line options: 

 

    •  ESX/ESXi 4.1 and earlier releases: vm-support -s -d <duration> -i <interval> 

       Note iconNote: If you want to collect only performance snapshots, without the regular data, use uppercase -S instead of lowercase -s.

 

    •  ESXi 5.0: vm-support -p -d <duration> -i <interval> 

 

If an interval is not specified, vm-support automatically sets the interval period to twice the amount of time taken to collect a single snapshot. For most cases, VMWare recommends that you set the interval period to 10 seconds.

 

The collected snapshots are bundled with regular data collected by vm-support, and a tar archive is created in /var/tmp/esx-2010-01-26--20.46.3236587.tgz. 

 

It is important that you use the vm-support script to capture performance snapshots when your system is experiencing a performance problem. The script cannot collect useful data otherwise. 

 

If the snapshot collection interval overlaps with a time when the virtual machine is not experiencing a performance problem, the result may skew the data collected and can make analysis difficult.


 


Additional Resources



This page was generated by the BrainKeeper Enterprise Wiki, © 2018