NSCA kinda... Monitored host to Nagios server info

[Richard A Nelson]

I've got a medium site monitored with Nagios, and really like the
changes in V2 :)

Here's one thing I have not been able to figure out how to handle:

I monitor service X on about a dozen machines
Some of those machines run testcases, which interfere with  service X
 	1) I want to stop notifications before running those testcases
 	2) I want to run the testcases, which corrupt, fill service X
 	   without flooding myself with mails
 	3) After the testcases are run, I want to re-enable notifications
 	4) This must all be scriptable

My first thought was NSCA, but I can't see how to have it do more than
the usual passive notification it seems designed for.

My next thought was to ssh from the monitored host to the server,
with a dedicated key (only able to start/stop notification), and have
a script on the monitoring server that dis/en-abled notifications.

The problem is that the ssh approach looks to work, but requires
different scripts, and keys for each scenario - I just don't seee
it scaling well.

Has anyone done something like this already ?
-- 
Rick Nelson
Life'll kill ya                         -- Warren Zevon
Then you'll be dead                     -- Life'll kill ya


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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