Monitors included into Virtual Machines – Hyper-V Hypervisor
The monitors from this application template check summary of Microsoft Hyper-V hypervisor status: total resources usage, included deposited pages, CPU utilization and traffic utilization, as well as list machines in critical status. Note that these monitors make use of WMI to collect data; thus, correct setting up WMI access is a mandatory prerequisite. More about templates.
Total CPU usage (enabled by default) Shows CPU usage of both hypervisor and guest machines (combined). Note that this metrics should be used to check for general system CPU usage (useful when controlling hardware temperature). Guest CPU usage should be used for control over guest machines.
Guest CPU usageShows CPU usage of all guest machines (combined). Use per-guest CPU usage monitor if you encounter CPU overload and need to find out which guest OSes are at fault.
Hypervisor CPU usageShows CPU usage of Hyper-V hypervisor. Under normal circumstances, there should be no frequent variations in this usage; noticeable drastic changes can indicate possible problems and should be attended to.
Virtual Machines in critical states (enabled by default) Shows the number of virtual machines requiring immediate attention (multiple issues can result in bringing VM to critical state – insufficient storage space or inconsistent storage state; internal VM problems; other host or guest OS-related issues). This monitor should be of higher importance in most situations.
Deposited pages (enabled by default) Deposited pages indicate how memory is being used by Hyper-V guests; the more pages are deposited, the less physical RAM is actually available for machines (swapping generally impacts efficiency negatively).
Network Traffic Speed (enabled by default) Monitors traffic speed on specified hypervisor’s virtual interface. Choose proper virtual interface to measure traffic speed related to guest machines in question (set interface name accordingly).
Network Traffic Volume (enabled by default) Monitors traffic volume on specified hypervisor’s virtual interface. As with speed monitor mentioned above, proper choice of virtual interface is required, to see the traffic data related to guests in question.
IPHost Network Monitor provides application templates (or just “templates” later in document), to create multiple relevant monitors in only a few clicks. Templates facilitate adding typical monitors sets; this can be particularly useful in case of big networks, when creating same-type monitors for many same-type devices is a common task. Application templates are sets of monitors that can be added, using specific predefined parameters, for a given host at once. The said set, added for given host, is displayed as a separate node in tree view pane, and is named application.
There are predefined templates; user can as well generate templates of their own – either out of existing monitors, or by cloning a predefined template. User-added template definitions are saved in XML files and can thus be conveniently augmented or applied to specific needs.