Passive Service not turning STALE
Posted: Fri Mar 08, 2019 10:06 am
Hi.
I have a passive check which is not changing state. Both boxes use ntp, times are matching.
I started by submitting manually a passive check result with Status OK, which is displayed correctly in the web gui. Since than I did not trigger any manual check from the remote side since I was expecting the service to trigger STALE state. But this does not happen. What am I doing wrong?
Thanks,
Steffi
These are the settings:
I have a passive check which is not changing state. Both boxes use ntp, times are matching.
I started by submitting manually a passive check result with Status OK, which is displayed correctly in the web gui. Since than I did not trigger any manual check from the remote side since I was expecting the service to trigger STALE state. But this does not happen. What am I doing wrong?
Thanks,
Steffi
These are the settings:
Code: Select all
define service {
host_name mail
service_description Remote Disk Space
check_period none
check_command check_dummy!2!"CRITICAL: Passive Check Results for Remote Disk Space were not reported!"
contact_groups admins
notification_period 24x7
initial_state o
importance 0
check_interval 3.000000
retry_interval 2.000000
max_check_attempts 3
is_volatile 0
parallelize_check 1
active_checks_enabled 1
passive_checks_enabled 1
obsess 1
event_handler_enabled 1
low_flap_threshold 0.000000
high_flap_threshold 0.000000
flap_detection_enabled 1
flap_detection_options a
freshness_threshold 60
check_freshness 1
notification_options r,w,u,c
notifications_enabled 1
notification_interval 60.000000
first_notification_delay 0.000000
stalking_options n
process_perf_data 1
retain_status_information 1
retain_nonstatus_information 1
}
Code: Select all
# check the "freshness" of service results. Enabling this option
# Values: 1 = enabled freshness checking, 0 = disable freshness checking
check_service_freshness=1
# check the "freshness" of service check results. If you have
# disabled service freshness checking, this option has no effect.
service_freshness_check_interval=60
# check the "freshness" of host results. Enabling this option
# Values: 1 = enabled freshness checking, 0 = disable freshness checking
check_host_freshness=1
# check the "freshness" of host check results. If you have
# disabled host freshness checking, this option has no effect.
host_freshness_check_interval=60
# will add to any host and service freshness thresholds that
additional_freshness_latency=15