"expire" a passive check result.

Rui Miguel Silva Seabra rms at sibs.pt
Tue Jan 8 17:56:40 CET 2008


Hello,

When using passive checks, you *should* do the following:
define service {
        name                            generic-passive-service ;
        active_checks_enabled           0       ; Active service checks are enabled
        passive_checks_enabled          1       ; Passive service checks are enabled/accepted
        parallelize_check               1       ;
        obsess_over_service             1       ;
        check_freshness                 1       ; Default is to NOT check service 'freshness'
        freshness_threshold             660
        is_volatile                     0
        notifications_enabled           1       ; Service notifications are enabled
        event_handler_enabled           1       ; Service event handler is enabled
        flap_detection_enabled          0       ; Flap detection is enabled
        process_perf_data               1       ; Process performance data
        retain_status_information       0       ; Retain status information across program restarts
        retain_nonstatus_information    0       ; Retain non-status information across program restarts

        register                        0       ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!

        check_period                    24x7
        max_check_attempts              2
        normal_check_interval           5
        retry_check_interval            1
        contact_groups                  admins
        notification_interval           0
        notification_period             24x7
        notification_options            w,u,c,r
        }

Notice in particular check_freshness and freshness_threshold!

Now on a service you have:

define service {
        use                             generic-passive-service

        host_name                       fubar
        service_description             Load
        is_volatile                     0
        check_command                   check-passive
}

Notice check_command?

define command {
        command_name    check-passive
        command_line    $USER1$/check_dummy 2 "No status update"
}

Helpful, though sparse, hints? :D

Rui

Ter, 2008-01-08 às 16:48 +0000, Jaime Ventura escreveu:
> Hello.
>     I have a system checking its own services and sending them to a 
> nagios server(passive checks).
>     But that system stopped sending results to the nagios server. Since 
> last availlable result was OK, nagios didnt warn me.
>     Is there any way to tell nagios  to set  the status  of a passive 
> check service to UNKNOWN, if a specified time passed since last received 
> result?
> 
>      Thanks,
>     Jaime

Or is it?
Today is Pungenday, the 8th day of Chaos in the YOLD 3174
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
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