<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Windows Pagefile Sensor

The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Management Instrumentation (WMI) or Windows performance counters, as configured in the Windows Compatibility Options of the parent device.

Windows Pagefile Sensor

Windows Pagefile Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: Windows Wisselbestand
  • French: Windows fichier d'échange
  • German: Windows Auslagerungsdatei
  • Japanese: Windows ページファイル
  • Portuguese: Arquivo de Paginação (Pagefile) Windows
  • Russian: Файл подкачки Windows
  • Simplified Chinese: Windows 页面文件
  • Spanish: Archivo de página Windows

Remarks

  • This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
  • This sensor requires at least Windows Server 2008 R2 on the probe system.
  • This sensor requires that the Remote Registry Windows service runs on the target system.
  • This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for target systems that run Windows Server 2016.
  • This sensor requires credentials for Windows systems in the settings of the parent device.
  • This sensor does not work with Windows 2000 because the respective WMI class does not exist on this operating system.
  • This sensor supports IPv6.

i_podYou 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.

Detailed Requirements

Requirement

Description

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).

i_round_redWoW64 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.

i_round_redIf 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.

Hybrid Approach: Performance Counters and WMI

i_round_blueBy default, this sensor uses WMI to request monitoring data. You can change the default behavior to a hybrid approach in the Windows Compatibility Options of the parent device's settings on which you create this sensor: if you choose this option, the sensor first tries to query data via Windows performance counters and uses WMI as a fallback if performance counters are not available. When running in fallback mode, the sensor tries to connect via performance counters again after 24 hours.

i_round_redSensors that use the WMI protocol have a high impact on the system performance. Try to stay below 200 WMI sensors per probe. Above this number, consider using multiple remote probes for load balancing.

i_round_blueFor a general introduction to the technology behind WMI, see section Monitoring via WMI.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

Setting

Description

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.

i_round_blueIf 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.

i_round_blueThis 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.

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

i_round_blueFor 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:

  • pagefilesensor
  • wmipagefilesensor

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 (i_priority_1) to the highest priority (i_priority_5).

Debug Options

Debug Options

Debug Options

Setting

Description

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 name is Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

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

Sensor Display

Sensor Display

Sensor Display

Setting

Description

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary 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.
    i_round_redYou 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.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

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

Total

The total pagefile usage (%)

i_round_blueThis channel is the primary channel by default.

i_round_blueThis channel has default limits

  • Upper error limit: 90%
  • Upper warning limit: 60%

More

i_square_blueKNOWLEDGE BASE

What security features does PRTG include?

My Windows sensors do not work when using direct performance counter access. What can I do?