Hi, When there is a problem on a host, and you have lots of services being check through a remote execution method like Nrpe, what do you do if Nrpe breaks or times out or something? You get flooded with alerts for all your systems. So, the solution to this is to create service dependencies that point back to one Nrpe service on the same machine, right? This way you only get 1 alert per machine instead of 10 alerts per machine...
Now the trick is, how do you go about creating a rack of service dependencies for all the remotely checked services via Nrpe for every host to depend on 1 Nrpe check on the same host? Bearing in mind that you don't want to be a mindless drone and create this by hand, and you certainly don't want to maintain this by hand for every host and all of their services... What do/would you do? -h -- Hari Sekhon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
