PRTG Manual: WMI Exchange Transport Queue Sensor
The WMI Exchange Transport Queue sensor monitors the length of transport queues of a Microsoft Exchange Server 2003 or later via Windows Management Instrumentation (WMI). It shows the same information as shown in Windows System Monitor perfmon.
The sensor can show the following:
- Active Mailbox Delivery Queue Length
- Active Non-Smtp Delivery Queue Length
- Active Remote Delivery Queue Length
- Aggregate Delivery Queue Length (All Queues)
- Aggregate Shadow Queue Length
- Categorizer Job Availability
- Items Completed Delivery Per Second
- Items Completed Delivery Total
- Items Deleted By Admin Total
- Items Queued For Delivery Expired Total
- Items Queued for Delivery Per Second
- Items Queued For Delivery Total
- Items Resubmitted Total
- Largest Delivery Queue Length
- Messages Completed Delivery Per Second
- Messages Completed Delivery Total
- Messages Completing Categorization
- Messages Deferred Due To Local Loop
- Messages Deferred during Categorization
- Messages Queued For Delivery
- Messages Queued for Delivery Per Second
- Messages Queued For Delivery Total
- Messages Submitted Per Second
- Messages Submitted Total
- Poison Queue Length
- Retry Mailbox Delivery Queue Length
- Retry Non-Smtp Delivery Queue Length
- Retry Remote Delivery Queue Length
- Shadow Queue Auto Discards Total
- Submission Queue Items Expired Total
- Submission Queue Length
- Unreachable Queue Length
Which channels the sensor actually shows might depend on the monitored device and the sensor setup.
For an explanation of transport queue types, see the Knowledge Base: What types of Exchange transport queues are there?
- Dutch: WMI Exchange Transport Wachtrij
- French: File d'attente de transport WMI Exchange
- German: WMI Exchange Transportwarteschlange
- Japanese: WMI Exchange 転送キュー
- Portuguese: Exchange Fila de transporte WMI
- Russian: Очередь транспорта WMI Exchange
- Simplified Chinese: WMI Exchange 传输队列
- Spanish: Cola de transporte WMI Exchange
- Sensors that use the WMI protocol have a high impact on system performance. Try to stay below 200 WMI sensors per probe. Above this number, consider using multiple remote probes for load balancing.
- This sensor requires credentials for Windows systems in the settings of the parent device.
- This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for target systems that run Windows Server 2016.
- This sensor supports the IPv6 protocol.
- This sensor has a high performance impact.
- See the Knowledge Base: What types of Exchange transport queues are there?
You cannot add this sensor to the hosted probe of a PRTG hosted by Paessler instance. If you want to use this sensor, add it to a remote probe device.
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you do not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.
Select the transport queues that you want to monitor. PRTG creates one sensor for each transport queue that you select in the Add Sensor dialog. The settings you select are valid for all sensors that you create when you finish this dialog.
The following settings in the Add Sensor dialog differ in comparison to the sensor's Settings tab.
WMI Exchange Transport Queue Specific
Setting |
Description |
---|---|
Transport Queues |
You see a list with the names of all items that you can monitor. Add check marks in front of the respective lines to select the desired items. You can also use the check box in the table header to select all items or cancel the selection.
The available options depend on your Exchange server configuration. PRTG shows all possible queues with names and instance descriptions (if available).
|
Click the Settings tab of a sensor to change its settings.
Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. See below for details on available settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a meaningful 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.
|
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is shown for your information only and cannot be changed here. |
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
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 ( |
WMI Exchange Transport Queue Specific
Setting |
Description |
---|---|
Display Name |
These fields show the parameters that are used to query data for this sensor from the target device. Once you have created the sensor, you cannot change this value. It is shown for reference purposes only. If you need to change this value, add the sensor anew. |
Instance |
|
WMI Class |
|
Counter |
|
Time Stamp |
|
Time Frequency |
|
Counter Type |
|
Result Handling |
Define what PRTG does with the sensor result:
|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. 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. |
By default, all of the following settings are inherited from objects that are higher in the hierarchy. You should change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance. You then see the options described below.
For more information, see section Inheritance of Settings.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Scanning Interval |
Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:
|
If a Sensor Query Fails |
Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:
|
Schedules, Dependencies, and Maintenance Window
You 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.
Setting |
Description |
---|---|
Schedule |
Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:
|
Maintenance Window |
Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:
|
Maintenance Begins |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window. |
Maintenance Ends |
This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window. |
Dependency Type |
Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
Dependency Delay (Sec.) |
This setting is only visible if you enable Select a sensor above. Define a time span in seconds for the dependency delay. After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
User Group Access |
Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
Channel Unit Types |
For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, these settings can be inherited to all sensors underneath. You can set units for the following channel types (if available):
|
KNOWLEDGE BASE
What types of Exchange transport queues are there?
My WMI sensors don't work. What can I do?
For more information about sensor settings, see the following sections: