<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Windows Print Queue Sensor
The Windows Print Queue sensor reads the print queue on the parent device and returns the number of jobs in the print queue. It can monitor queues for all printers that are locally installed.
You can use this sensor to monitor all print queues on your Windows print server and to retrieve information about all available jobs that are in the queue longer than defined.
Additionally, this sensor can change to a defined status if there is a printer problem. See section Sensor Settings for available parameters.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Windows Print Queue Sensor
Sensor in Other Languages
- Dutch: Windows Print Queue
- French: File d'attente d'impression Windows
- German: Windows Druckwarteschlange
- Japanese: Windows プリントキュー
- Portuguese: Windows Fila de impressão
- Russian: Очередь печати Windows
- Simplified Chinese: Windows 打印队列
- Spanish: Queue de impresión Windows
Remarks
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.
Detailed Requirements
|
|
.NET Framework
|
This sensor requires the Microsoft .NET Framework. .NET 4.7.2 or later must be installed on the probe system (on every cluster node, if on a cluster probe).
If the framework is missing, you cannot create this sensor.
For more information, see the Knowledge Base: Which .NET version does PRTG require?
|
Windows credentials
|
This sensor requires credentials for Windows systems in the settings of the parent device. Preferably, 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 computer. Otherwise, the sensor cannot correctly connect.
|
Print Spooler service
|
For this sensor to work, the Spooler "Print Spooler" service must be started on the target computer.
To enable the service, log in to the respective computer and open the services manager (for example, via services.msc). In the list, find the respective service and set its Start Type to Automatic.
|
Add Sensor
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. Therefore, you do not see all settings in this dialog. You can change nearly all settings on the sensor's Settings tab after creation.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
Sensor Settings
|
|
Print Queues
|
Select the print queues that you want to monitor. PRTG creates one sensor for each print queue that you select.
If no print queues are available, you see a corresponding message.
If a printer name changes after sensor creation, you need to add the sensor anew.
Add check marks in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.
|
Basic Sensor Settings
Click the Settings tab of a sensor to change its settings.
Basic Sensor Settings
|
|
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.
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
|
Shows 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:
|
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 ().
|
Usually, a sensor connects to the IP Address or DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
Sensor Settings
Sensor Settings
|
|
Print Queue
|
Shows the name of the task whose print queue this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Advanced Status Options
|
You can optionally define specific sensor states for several return messages of the printer that this sensor monitors. Choose between:
- Do not define sensor states for specific return messages: Do not define sensor states for specific return messages.
- Define sensor states for specific return messages: Define sensor states for various messages that the printer reports.
Not all printer types properly support Advanced Status Options, which might lead to false alerts. If the printer does not support a property, this property is always false. This means that the sensor cannot display the state or detect if the printer supports the property. Even if the printer can report a property, it can only do so if a print job is sent to the printer.
|
Door Open
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Manual Feed Required
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Needs User Intervention
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Offline
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Out of Memory
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Out of Paper
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Paper Jammed
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Paper Problem
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Paused
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Printer Error
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Printer Not Available
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Toner Low
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Toner Out
|
This setting is only available if you select the Define sensor states for specific return messages above. For each problem that the printer reports, you can define the status that the sensor shows. Choose between:
- Ignore: Stay the same if the printer reports this message.
- Warning: Show the Warning status if the printer reports this message.
- Down: Show the Down status if the printer reports this message.
|
Minimum Print Job Age (Sec.)
|
Optionally define the age of the print job in seconds. If you define a minimum print job age, the sensor does not regard jobs that are younger than this value. If you leave this field empty, the sensor does not check for the print job age. Enter an integer value or leave the field empty.
|
Debug Options
Debug Options
|
|
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.
|
Sensor Display
Sensor Display
|
|
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 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.
|
Inherited Settings
By default, all of the following 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 under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
Scanning Interval
Click to interrupt the inheritance.
Scanning Interval
|
|
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:
- 30 seconds
- 60 seconds
- 5 minutes
- 10 minutes
- 15 minutes
- 30 minutes
- 1 hour
- 4 hours
- 6 hours
- 12 hours
- 24 hours
You can change the available intervals in the system administration on PRTG on premises installations.
|
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:
- Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
- Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
- Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
- Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
- Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
- Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.
Sensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show the Down status. It is not possible to immediately set a WMI sensor to the Down status, so the first option does not apply to these sensors. All other options can apply.
If you define error limits for a sensor's channels, the sensor immediately shows the Down status. None of the interval options apply.
If a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.
|
Schedules, Dependencies, and Maintenance Windows
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.
Schedules, Dependencies, and Maintenance Windows
|
|
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:
- None
- Saturdays
- Sundays
- Weekdays
- Weekdays Eight-To-Eight (08:00 - 20:00)
- Weekdays Nights (17:00 - 09:00)
- Weekdays Nights (20:00 - 08:00)
- Weekdays Nine-To-Five (09:00 - 17:00)
- Weekends
You can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Schedules.
|
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:
- Do not set up a one-time maintenance window: Do not set up a one-time maintenance window. Monitoring is always active.
- Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for the pause below.
To terminate an active maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.
|
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:
- Use parent: Use the dependency type of the parent object.
- Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if a specific sensor is in the Down status or in the Paused status because of another dependency.
- Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in the Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.
To test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.
|
Dependency
|
This setting is only visible if you enable Select a sensor above. Click and use the object selector to select a sensor on which the current object will depend.
|
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.
This setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.
|
Access Rights
Click to interrupt the inheritance.
Access Rights
|
|
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:
- Inherited: Inherit the access rights settings of the parent object.
- No access: Users in this user group cannot see or edit the sensor. The sensor neither shows up in lists nor in the device tree.
- Read access: Users in this group can see the sensor and view its monitoring results. They cannot edit any settings.
- Write access: Users in this group can see the sensor, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
- Full access: Users in this group can see the sensor, view its monitoring results, edit its settings, and edit its access rights settings.
For more details on access rights, see section Access Rights Management.
|
Channel List
Which channels the sensor actually shows might depend on the monitored device, the available components, and the sensor setup.
|
|
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 in percent.
|
Execution Time
|
The execution time in milliseconds (msec)
|
Jobs
|
The number of jobs in the queue
This channel is the primary channel by default.
|
More
KNOWLEDGE BASE
Which .NET version does PRTG require?
What security features does PRTG include?
Sensor Settings Overview
For more information about sensor settings, see the following sections: