I'll give that a shot, another question I have on the 1/1 checks I set up... They're being labeled by XI as soft 1/1, shouldn't those be Hard?
Can you show us how this host is defined? Also, show us the State History report for this host (State Types = Both; Host/Service = Hosts).
Consider the following scenario - in your host definition, you have:
Code: Select all
max_check_attempts 1
check_interval 1
retry_interval 1
When the host is detected to be in a non-OK state, during the regular check interval (every minute), the host will switch to a soft down state.
THIS IS THE FIRST CHECK (run on the regular "check_interval" schedule)
After this, the "retry_interval" will kick in (which is also 1 min). After the number of "max_check_attempts" (which is also one minute), the host will switch to a hard down state.
THIS IS THE SECOND CHECK (run on the "retry_interval" schedule)
This is the default (expected) behavior.
Host - retry interval
This directive is used to define the number of "time units" to wait before scheduling a re-check of the hosts. Hosts are rescheduled at the retry interval when they have changed to a non-UP state. Once the host has been retried max_check_attempts times without a change in its status, it will revert to being scheduled at its "normal" rate as defined by the check_interval value. Unless you've changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.
Are you seeing something else?
