Want this feature implemented, too? Please upvote by clicking Thumbs up!
(Posts as a reply won't be published in this feature request thread. Read Me!)
In order to properly monitor Hyper-V performance and detect overprovisioning or malfunctions it is crucial to monitor the "CPU Time per Dispatch" metric for each VM.
Details of user story
CPU Time per dispatch is Hyper-V's closest relative to CPU Ready metric which is included in the VMware Virtual Machine (SOAP) and VMware Host Performance (SOAP) sensors of PRTG.
Every Hyper-V sysadmin should be able to monitor this metric to detect possible overprovisioning, malfunctions or misconfigurations on a Hyper-V environment and take proper actions proactively for both each hypervisor and each VM independently.
- New channel in the Hyper-V Virtual Machine sensor type that includes the CPU Wait Time Per Dispatch metric for the relevant VM.
- New channel in the Hyper-V Host Server sensor type that includes the CPU Wait Time Per Dispatch metric for the relevant hypervisor.
- The values may well be the deltas to the previous read values, or alternatively, a "speed" metric type, as the raw data provided by Hyper-V system is an increasing counter.
- PRTG user must have the ability to set thresholds on the "delta" or "speed" values of the above mentioned channels.