vSphere/ESX Host Monitoring
- What is the CPU load on the ESX kernel, on the console, and each of the virtual guests?
- What is the free memory in the ESX kernel and the console?
- Which network interfaces are seeing the most traffic?
- Which storage devices are seeing high activity?
- How much free space is available on each of the disk partitions?
- Are there processes on the console VM that are taking up excessive resources?
Virtual Guests Monitoring
- How many guest virtual machines are running? What are their IP addresses/host names and operating systems?
- What portion of the vSphere/ESX server’s CPU is used by each guest?
- Are there times when a guest VM is not getting CPU cycles; i.e., is the ready time too high?
- How much of the memory allocated is a guest VM actively using?
- Is the balloon driver enabled for a guest VM, and how much memory has it freed for each guest VM?
- Which processes on a guest VM are taking up high disk, CPU or memory resources?
- Is there excessive paging or memory thrashing in a guest VM?
- Do all the disk partitions inside the guest operating system have adequate space?
- Is there excessive queuing for disk access on any guest operating system? Which applications could be causing these accesses?
Virtual Desktop Monitoring
- How many desktops are powered on simultaneously on the ESX Server?
- Which users are logged on and when did each user login?
- How much CPU, memory, disk and network resources is each desktop taking?
- What is the typical duration of a user session?
- Who has the peak usage times?
- What applications are running on each desktop?
- Which vSphere/ESX server is a virtual guest running on?
- When was a guest moved from an vSphere/ESX server? Which ESX server was the guest moved to?
- Why was the guest VM migrated? What activities on the vSphere/ESX host caused the migration?