Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_printers
Owner
Website
Hits
159958
Files:
| File | Description |
|---|---|
| INSTALL.txt | install instructions |
| check_printer.tar.gz | plugin source |
| check_printers.diff | patch against nagios-plugins-1.4 |
| check_printer.tar.gz | plugin source - update v0.13 |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
inspired by check_hpjd from the original nagios-plugins, I've written this plugin.
It queries prtAlertTable from the Printer MIB.
It honors only prtAlertTrainingLevel = trained(4) or fieldService(5),prtAlertTrainingLevel = other(1),unknown(2),untrained(3) and management(6) are ignored.
For prtAlertSeverityLevel = warning(4) the plugin result is "WARNING",
for critical(3) the plugin result is "CRITICAL", obviously,
for warningBinaryChangeEvent(5) (new in RFC3805) the state is by default "WARNING", but there is a hardcoded table of change events, which result in state "CRITICAL"
I'm using it to monitor 35+ printers (mostly HP, but also Kyocera and Epson) for things like toner state, paper jam and hardware errors.
empty paper trays are not monitored, that can be done by users themselve ;-)
It queries prtAlertTable from the Printer MIB.
It honors only prtAlertTrainingLevel = trained(4) or fieldService(5),prtAlertTrainingLevel = other(1),unknown(2),untrained(3) and management(6) are ignored.
For prtAlertSeverityLevel = warning(4) the plugin result is "WARNING",
for critical(3) the plugin result is "CRITICAL", obviously,
for warningBinaryChangeEvent(5) (new in RFC3805) the state is by default "WARNING", but there is a hardcoded table of change events, which result in state "CRITICAL"
I'm using it to monitor 35+ printers (mostly HP, but also Kyocera and Epson) for things like toner state, paper jam and hardware errors.
empty paper trays are not monitored, that can be done by users themselve ;-)
