Hi all,
Right, so I've got everything configured just as I want it. The only problem I have is with notifications via email. It all works, the issue is that I don't want to know if the printer has been switched off but I do want to know if the toner is out or a paper jam, etc has occurred. So, I've disabled notifications for PING failures and have also removed the check_command check_host_alive command from the generic-printer host definition that each of the printers are using. This has done the job and I am not being notified about the printer being down, however, as I still have notifications enabled on the printer statuses and the toner (because I want to know about them), when the printer is off, I get multiple notifications about there being no SNMP response from X.X.X.X. Make sure host is up and SNMP is configured properly.
How can I keep the notifications enabled but prevent them from moaning at me when it can't get any SNMP response from the device?
Thanks for any pointers you can give.
**Turns out that switching off the notifications didn't work after all. Constant emails about the printer being off too, despite the Ping service set up to "not notify". What gives?!
Too many printer notifications!
Re: Too many printer notifications!
I believe that if you don't specify a check command for your host it will default to check_host_alive... I'm not event 80% sure about that as I've never attempted to remove the host check_command, so I wouldn't quote me on it. As a result I believe you are probably getting notifications from the host and not from the ping service you have disabled notifications on. Would you be able to post up the config for your host-template, host and ping service, that might help remove the guess work from diagnosing the problem?
As for the SNMP notifications issues... a lot of plugins have an option that will make the check return unknown instead of critical for communications failures. For those that don't, I tell the plugin authors that they are bad people and write a wrapper script that will do a regex match on "host down" type messages and return unknown (exit code of 3) instead.
As for the SNMP notifications issues... a lot of plugins have an option that will make the check return unknown instead of critical for communications failures. For those that don't, I tell the plugin authors that they are bad people and write a wrapper script that will do a regex match on "host down" type messages and return unknown (exit code of 3) instead.