On Wed, 8 Feb 2006, Deborah Martin wrote:

Hi,

I have dependencies working mainly fine. However, i'm still not 100%
satisfied that its behaving correctly.

Using Nagios 2.0rc2 on suse 9.2 (i've used later releases for testing but
behaviour is the same)

I have one main service which is a database connection plugin to ensure the
database is up and running.
I have 3 additional dependency plugins which do various other checks such as
ram and disk usage.

When the main database plugin check goes to warning or critical I want to
suppress email notifications on the 3 remaining checks as there is no point
in running these (they won't return anything useful apart from timeouts).

However, this rarely happens. Usually, I get the main check email
notification plus 1 other email notification from one of the dependencies
(though it may not always be the same dependency)

Is there something i'm missing here ? Why can't it supress all three as i
would expect ? Do i need to set a parameter setting somewhere ?

My main plugin checks every 5 mins with the dependencies every 20 mins.
Should i change these timings to something different and if so why ?

This is driving me somewhat insane and any pointers / help would be very
welcomed.

regards,
deborah


It is possible for the checks to be running concurrently - If the main check fails, then the service dependency checks kick in. but the cocurrent check is already in progress and notifications would be sent out.

-sg

--




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users@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

Reply via email to