PRTG Manual: Hyper-V Virtual Machine Sensor

Windows version

To work with Windows performance counters, this sensor requires that at least Windows Server 2008 R2 is installed 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

To work with Windows performance counters,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.

Windows credentials

This sensor requires credentials for Windows systems in the settings of the parent device. 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.

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• wmihypervsensor

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

GUID

The globally unique identifier (GUID) of the VM that this sensor monitors.

Virtual Machine Name

The name of the VM that this sensor monitors.

Description

The description of the VM that this sensor monitors.

Powered-Off VM Handling

Define how the sensor reacts to VMs that are powered off:

• Alarm when VM is powered off (default): Change to the Down status if the VM is powered off.

If the sensor is in the Down status, it does not record any data in any of its channels.

• Ignore powered off state: Do not change to the Down status if the VM is powered off. The sensor reports zero values instead.

Result Handling

Define what PRTG does with the sensor result:

• Discard result: 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, the last value of the primary channel is always displayed 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 different channels are shown for this sensor:

• 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. All channels with this unit are stacked 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 Guest

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.

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

IDE: Read Bytes/Sec

The disk read speed of the IDE

IDE: Write Bytes/Sec

The disk write speed of the IDE