Monitors included into Virtual Machines – Hyper-V Virtual machine
The monitors from this application template watch summary of Microsoft Hyper-V Virtual Machine status: CPU and memory utilization, uptime counter and network traffic and speed measurement. These monitors make use of WMI, thus correct setting up WMI access is a mandatory prerequisite. More about templates.
NB: for the below monitors, set ‘Virtual Machine Name’ parameter, if present, to actual virtual machine name.
Uptime (enabled by default) Reports uptime for a virtual machine.
CPU load (enabled by default) Reports CPU utilization for given virtual machine.
Available Memory Shows percentage of memory available to virtual machine (referring assigned memory).
Memory Demand (enabled by default) Shows actual memory usage by the virtual machine.
Assigned Memory Shows amount of memory assigned to virtual machine by hypervisor.
Network Traffic Speed (enabled by default) Monitors traffic speed on specified hypervisor’s virtual interface. Set ‘Interface Name’ as required, to measure traffic speed related to specified guest machine.
Network Traffic Volume (enabled by default) Monitors traffic volume on specified hypervisor’s virtual interface. As with speed monitor mentioned above, set proper virtual interface name to see the traffic data related to given virtual machine.
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.