Relation between Freshness Check period and service check period

Sumit Malhotra smalhotra at dataarmor.net
Wed Jun 16 12:17:40 CEST 2004


Hi ,

 Is there any relation between freshness check period and service check period ??

 I have observed both work independently i.e. if the freshnesss check is 10 minutes and service check period is 16*5  
The active check(check_command) will be executed out of the service check period(16*5) Am i missing something ???

Thanks in advance.
Regards,
Sumit

#####
define service {
name                           generic-service-passive ; The 'name' of this service template, referenced in other service definitions
active_checks_enabled          0       ; Active service checks are enabled
passive_checks_enabled         1       ; Passive service checks are enabled/accepted
parallelize_check              1       ; Active service checks should be parallelized (disabling this can lead to major performance problems)
obsess_over_service            1       ; We should obsess over this service (if necessary)
check_freshness                1       ; Default is to NOT check service 'freshness'
freshness_threshold     1800    ; default 15 minutes
check_command           no-report
notifications_enabled          1       ; Service notifications are enabled
event_handler_enabled          1       ; Service event handler is enabled
flap_detection_enabled         1       ; Flap detection is enabled
process_perf_data              1       ; Process performance data
retain_status_information      1       ; Retain status information across program restarts
retain_nonstatus_information   1       ; Retain non-status information across program restarts
register                       0       ; DONT REgISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}


define service {
use                            generic-service-passive         ; Name of service template to use
host_name                      ABC
service_description            report
is_volatile                    0
check_period                   24x7
max_check_attempts             3
normal_check_interval          5
retry_check_interval           1
contact_groups                 admins
notification_interval          120
notification_period            24x7
notification_options           w,u,c,r
freshness_threshold     600
check_command           no-report
}



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040616/450eecd9/attachment.html>


More information about the Users mailing list