Nagios ignoring notification interval with passive checks

[Subhendu Ghosh]

"Volatile services are useful for monitoring...

     * things that automatically reset themselves to an "OK" state each 
time they are checked
     * events such as security alerts which require attention every time 
there is a problem (and not just the first time)
"

Volatile override all interval settings.  If you want the intervals to be 
honored, then use just "passive" not "passive + volatile"

-sg

On Mon, 13 Jun 2005, Andreas Wassatsch wrote:

>
> Hello list,
>
> I've setup a passive check which submits its return value every minute
> to Nagios.
>
> The Problem is: When the passive_check submits a critical or warning
> result to Nagios every minute, Nagios is ignoring the
> notification_interval and sends out a notification every minute.
>
> Is there a way to get Nagios honoring notification_interval with
> passive_checks ?
>
> Regards,
> Andreas
>
>
> Nagios: 2.0b3
>
> define service {
>        use                             active-service
>        name                            passive-service
>        is_volatile                     1
>        passive_checks_enabled          1
>        max_check_attempts              1
>        normal_check_interval           1
>        retry_check_interval            1
>        notification_interval           120     ; 2h
>        active_checks_enabled           0
>        check_command                   none
>        check_period                    none
>        check_freshness         1
>        register                        0
> }
>
> define service {
>        use                     passive-service
>        name                    passive-service-frasw-core1
>        host_name               frasw-core1
>        contact_groups          network-admins
>        register                0
> }
>
> define service {
>        use                     passive-service-frasw-core1
>        service_description     if-gig1.13
>        contact_groups          network-admins-test
> }
>
> # tail -f var/nagios.log
> [1118669106] EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;frasw-core1;if-gig1.13;2;CRITICAL: Interface
> gig1.13 (Link to frasw-dist-giga idx=13) is down
> [1118669116] SERVICE ALERT:
> frasw-core1;if-gig1.13;CRITICAL;HARD;1;CRITICAL: Interface gig1.13 (Link
> to frasw-dist-giga idx=13) is down
> [1118669116] SERVICE NOTIFICATION:
> andreas.wassatsch-test;frasw-core1;if-gig1.13;CRITICAL;notify-by-email;CRITICAL:
> Interface gig1.13 (Link to frasw-dist-giga idx=13) is down
> [1118669168] EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;frasw-core1;if-gig1.13;2;CRITICAL: Interface
> gig1.13 (Link to frasw-dist-giga idx=13) is down
> [1118669176] SERVICE ALERT:
> frasw-core1;if-gig1.13;CRITICAL;HARD;1;CRITICAL: Interface gig1.13 (Link
> to frasw-dist-giga idx=13) is down
> [1118669176] SERVICE NOTIFICATION:
> andreas.wassatsch-test;frasw-core1;if-gig1.13;CRITICAL;notify-by-email;CRITICAL:
> Interface gig1.13 (Link to frasw-dist-giga idx=13) is down
> [1118669226] EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;frasw-core1;if-gig1.13;2;CRITICAL: Interface
> gig1.13 (Link to frasw-dist-giga idx=13) is down
> [1118669236] SERVICE ALERT:
> frasw-core1;if-gig1.13;CRITICAL;HARD;1;CRITICAL: Interface gig1.13 (Link
> to frasw-dist-giga idx=13) is down
> [1118669236] SERVICE NOTIFICATION:
> andreas.wassatsch-test;frasw-core1;if-gig1.13;CRITICAL;notify-by-email;CRITICAL:
> Interface gig1.13 (Link to frasw-dist-giga idx=13) is down
>
>

-- 



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
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