Additional Hyper-V polling information

A wealth of information present in the Hyper-V performance counters does not appear to be polled by VMan currently;

Some very specific examples are
Hyper-V Hypervisor Root Virtual Processor \ %Remote Run Time
CPU Wait Time Per Dispatch

Remote Runtime being a counter showing the time a vCPU access resources in another numa node. (As I understand it)

CPU Wait Time Per Dispatch being analgous to the Ready or Co-Stop time in Vmware.

These are standard windows performance counters which I suppose could be polled with SAM but they are explicitly Virtualization specific counters which I expect to be in VMAN.

So am I missing these somewhere, or is this an enhancement request?

  • I am relatively new to both Hyper-V and VMAN, having worked in both VMWare and Nutanix environments. I am just getting around to focusing on this stuff in my new role, and I am beginning to realize that Solarwinds overall support for Hyper-V host monitoring seems really, REALLY, limited. Any yet no one seems to be talking about it. 

    I'm really hoping someone will point me in the direction of a wealth of information on how to accurately monitor Hyper-V hosts in the Solarwinds suite of products, but I am not able to find much at all. Hyper-V host performance monitoring is a high priority for our organization, but I'm wondering if VMAN is really an adequate tool for it. I have always understood that it was really designed primarily for VMWare, but as it is highly advertised as a solution for Hyper-V as well, I assumed it provided at least the basic information.

    Are we all missing something? Because as it stands, I don't see a great deal of value in using VMAN in a Hyper-V environment.

    I am happy to be corrected.

  • So, yeah. There is more information here than it at first appears, but you do have to dig for it. Maybe it wouldn't be so difficult if we didn't have so many modules licensed, but there you have it.

    I realize that there are reports and alerts that are based on Virtual Host CPU load, and I am creating some custom widget to display that information. I will be delving into this in more detail. I guess my issue is that VMAN information for Hyper-V just doesn't appear to be that well discussed and or documented. But it is there if you look for it.

    But back to 's original question (sorry for co-opting your thread to complain), I agree that the more pertinent statistics for Hyper-V should somehow be incorporated into that statistics that VMAN collects and reports. If you have access to SAM we should be able to access that data that way, and that is where I will probably focus my attention. If I can get it all together I'll see if I can put together a custom application template that monitors key Hyper-V performance statistics. It doesn't help if you don't have a SAM license, however, but I don't see an alternative.