With ESXTOP or the vCenter performance tab of a VM you can monitor the co-stop metric to check for vSMP performance problems. vCOps can show you that information for all the VMs on a host, a resource pool, a cluster, a vCenter or your complete environment.
During the vCenter installation process you can config a custom http port. This can be needed because of security policies or if a other service uses port 80, but it leads to errors afterwards.
In the vSphere client performance tab of a virtual machine you can monitor the CPU Wait time, but it’s counted for every vCPU and no percentage metric is provided. vCenter Operations can solve that problem for you.
vCenter Operations provides different widgets to display the data collected from vCenter, storage systems or other data sources. Using the example of finding out which of the VMs in a vCenter are affected by high cpu ready % values i show you how to use heatmaps, metric graphs and data distribution widgets.
Earlier this year i have found two errors within the Get-DistributedSwitchPortGroup cmdlet from the book “The VMware vSphere PowerCLI Reference: Automating vSphere Administration”. The book is a great resource for automating vSphere environments and the scripts extend PowerCLI with the missing dvSwitch cmdlets and other useful stuff.