email alert only after duration

Fredrik Wänglund fredrik.wanglund at mobeon.com
Thu Mar 25 09:18:41 CET 2004


You can use the parameters 'retry_check_interval' and 
'max_check_attempts'. If, for example 'retry_check_interval' is set to 1 
and 'max_check_attempts' is set to 3, the alert will be delayed three 
minutes (The CPU-load must results in a warning or critical state during 
the whole period)

/FredrikW


Neil wrote:

> Hey guys. I am currently monitoring cpu utilization. How will I 
> configure nagios so that when cpu utilization hits at 80% continuously 
> after 3 or 5 minutes, nagios will only send an email alert if it notices 
> that cpu utilization was consistenly above 80% for more than 3 minutes?
> Thanks in advance.
> Neil
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> 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



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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





More information about the Users mailing list