Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #7354] Disable immediate hard state after first checkresult #2039
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7354
Created by arcade on 2014-10-08 11:53:54 +00:00
It would be nice that when you configure a new service/hostcheck and this check returns something different than "OK/UP" for the first checkresult, the service/host should stay in a soft state and not switch to a hard state immediately as it does now.
The same behaviour as it already is in Icinga 1, even though the first checkresult fails, it has to reach the max_check_attempts before the service/host switch to a hard state.
2016-08-04 14:16:58 +00:00 by mfriedrich 3f89a6d
Updated by mfriedrich on 2016-03-11 08:39:20 +00:00
If we change that behaviour, we must
Updated by mfriedrich on 2016-08-04 13:52:48 +00:00
Can be reproduced with max_check_attempts = 2 and a passive check result on a pending host check.
This immediately changes to a hard state, but does not trigger any notifications (it is not recognised as hardStateChange). Since this affects the way how users tend to interpret notifications from hard states (no notification was sent even if the web interface says "HARD 1/2") I'm changing this behaviour with 2.5.
I'm testing this as part of resolving the remaining notification issues, currently with #10363.