Tom, On 25 February 2011 10:36, Tom Elliott - Gyron <[email protected]> wrote: > Ideally what I'd like to be able to do is either: > > - Monitor all the points, but have the non-response not be an error
Would the following plugin help? http://exchange.nagios.org/directory/Plugins/System-Metrics/Networking/Check_snmp-INVERTER/details You can create something similar whereby you could set the "UNKNOWN" (code 255) return as being the "OK" state. It's a shame it comes up with "no such name" - implies it would fail-dangerous. Worth putting a comparison in there to make sure you're matching against the right string. > - Only monitor certain service checks when the 'number of alarms' service > check is critical This is something I considered "back in the day" as a notification mechanism for Nagios - it would cause a series of passive checks to be run which would feed back into Nagios. If any came back with critical, it would remain that way until manually cleared though, it wouldn't "re-check". The simplest way to do it might be to just create a shell script that does the first SNMP check, and if that comes back critical, to then enter an if loop that went out and checked the rest of the OIDs etc. Use the script I posted above to see an example of how to do that. Hope that helps! M _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
