PRTG Manual: Hyper-V Host Server Sensor

Performance impact

This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.

Windows version

This sensor requires at least Windows Server 2008 R2 on the probe system (on every cluster node, if on a cluster probe).

WoW64 must be installed on target systems that run Windows Server 2016. This allows 32-bit applications to be run on 64-bit systems. This is necessary because the PRTG probe service only runs with 32-bit support. Without it, WMI sensors do not work.

Remote Registry Windows service

This sensor requires that the Remote Registry Windows service runs on the target system.

If this service does not run, a connection via performance counters is not possible. However, WMI connections might still work.

To enable the service, log in to the respective system and open the services manager (for example, via services.msc). In the list, find the respective service and set its Start Type to Automatic.

Parent device

This sensor requires that the parent device is a Windows server that runs Hyper-V.

Credentials

This sensor requires credentials for Windows systems.

We recommend that you use Windows domain credentials. If you use local credentials, make sure that the same Windows user accounts (with the same user name and password) exist on both the probe system and the target system.

Otherwise, a connection via performance counters is not possible. However, WMI connections might still work.

IPv6

This sensor supports IPv6.

Hosted probe

You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.
• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

CPU Usage Guests

The CPU usage of the guests (%)

CPU Usage Hypervisor

The CPU usage of the hypervisor (%)

CPU Usage Total

The total CPU usage

This channel is the primary channel by default.

Deposited Pages

The number of deposited pages

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Host Health Critical

The number of host health-critical values

Network Traffic

The sum of the total bytes (received and sent) on all ports of the virtual switch