The target user for this use case is the VM Owner (via the operations team).
It is common for the application team (or the VM Owner) to suspect that virtualization is behind any performance degradation. After all, resources are shared and there are many IaaS workloads.
The workflow here is that the operations team gets a call from a VM Owner asking for proof on whether or not the VM is being held back by the infrastructure. In other words, does the infrastructure give whatever resources the VM is asking for? To prove this, we need to show the following information about the VM:
CPU contention
Memory contention
Disk latency
Network dropped packets (as covered at the beginning of Chapter 6, Network Counters, vCenter does not provide network latency information)
All the preceding information has to be provided in a line chart format, so that any peak in the past can be shown. The line chart will also enable the operations team to look back to see whether...