PRTG Manual: WMI Vital System Data v2 Sensor

Performance impact

This sensor has a high performance impact. Stay below 200 WMI sensors per probe. Above this number, consider using multiple remote probes for load balancing.

WoW64

This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for target systems that run Windows Server 2016.

Credentials

This sensor requires credentials for Windows systems.

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.

Performance Counter

Select the performance counters that you want to monitor. PRTG creates one sensor for each counter that you select.

You see a list of available vital system data values the sensor can monitor on the target device. The available options depend on your configuration. PRTG shows all possible performance counters with the name and instance description (if available).

Choose from the following counters:

• CPU
• Thread
• Memory
• Network
• Pagefile

Display Name

The display name that the sensor uses to query data from the target device.

Instance

The instance that the sensor uses to query data from the target device.

WMI Class

The WMI class that the sensor uses to query data from the target device.

Counter

The counter that the sensor uses to query data from the target device.

Time Stamp

The time stamp that the sensor uses to query data from the target device.

Time Frequency

The time frequency that the sensor uses to query data from the target device.

Counter Type

The counter type that the sensor uses to query data from the target device.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.
• Store result: Store the sensor result and the last response 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.

Bytes In All Heaps

The CLR memory bytes in all heaps

Bytes Total/Sec

The total number of bytes per second

Committed

The committed bytes

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.

Excepts

The number of thrown CLR exceptions

Free Physical Memory

The free physical memory

Packets Outbound Errors

The number of outbound packet errors

Queue Length

The CPU queue length

Total Visible Memory

The total visible memory

User Time

The CPU user time (%)