On 2 July 2010 00:56, Jaden Bentley <[email protected]> wrote: > Hello, > One of the services we monitor is a web server which we've installed bot > detection on. The bot detection works by looking at the standard deviation > of requests from a specific host. We don't want our own monitoring to get > blocked by our bot detection script, and for a variety of reasons, we don't > want to deal with putting in exceptions in our bot detection system. > We used to monitor with a manually written script. It was easy then: it ran > in a loop, and after each check, it would sleep for 5 minutes plus another > 0-300 seconds, with the specific number of seconds chosen at random. > We're having trouble porting this into our shiny new nagios monitoring > system. > The only idea I've had so far involves changing the service check interval > to something large (say 60 minutes), as a 'fallback' in case of failure, and > then having the service check itself re-schedule itself by sending nagios a > command. I'm not sure that would work and it seems pretty ugly and I'm not > sure if it would be that easy to implement (mostly because I haven't worked > with manual nagios commands before). > Can anyone think of a better way?
You can set up the check as a passive check in Nagios. Run the check from a similar looping script like you had before to do the random timing stuff and have it send the result back to nagios either directly using the command interface or using send_nsca and have nsca submit the result to Nagios. See: http://nagios.sourceforge.net/docs/3_0/passivechecks.html and the nsca_wrapper script is useful for such stuff. See: http://exchange.nagios.org/directory/Addons/Passive-Checks/NSCA-Wrapper/details ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
