...
For tenants that require constant use of printers for critical workflows, IT-Conductor provides the solution for monitoring, alerting, and recovering the printer for uninterrupted printingyou have the option to automate the process of restarting printer queues using IT-Conductor’s recovery action.
Pre-requisite Requirements
The printer(s) should be registered for monitoring in IT-Conductor .
IT-Conductor pulls printer statistics like status, request count, and request age.
...
Users can drill down to any stats and change the timescale as required,
...
Alerting
IT-Conductor generates alerts based on the values of collected stats.
...
In the above configuration, the warning alert is generated if the average request count is more than 1 in the last 15 minutes and the alert is resent if after 15 minutes there are still jobs running.
...
Similarly, in figure 5 configuration, the critical alarm alert is generated if the job has been running for more than 60 minutes (3600 seconds) and the alert is resent if after 60 minutes there are still jobs running.
Recovering
...
for monitoring. See OS Printer Monitoring for more details.
How to Automate OS Printer Queue Restart
When configuring printer alerts, the following command as shown in the SSH tab should handle the recovery action needed to restart a printer.
...
Simple ssh script that runs as ITC activity is called during recovery action.
We identified that the status of the printer could be any one of the following:
...
In the above configuration, the recovery action is triggered when the printer's status goes to “Disabled“ and is relaunched if after 10 minutes it's still in “Disabled“ status.
...
Simple ssh script that runs as ITC activity is called during recovery action.