Icinga2 seems to have an unbalanced way of treating HARD and SOFT states.

I am using a max_checks value of 3 for a service.  Let's say that a service 
goes into a SOFT Warning or Critical state (i.e. the problem occurs for less 
than 3 checks in a row, in my case).  Then the service recovers.  It will first 
go into a SOFT OK state, then into a HARD OK state.  This occurs even though it 
never entered a HARD Warning or Critical state.

My service frequently goes into a SOFT non-OK state, but it almost never goes 
into a HARD non-OK state, because the problem rarely occurs 3 times in 
succession.  This is by design.  However, if it does, there's a real problem, 
and that's what I want the HARD state to show - the real problem, and then the 
real recovery from that problem.

To my end-user, I only want to show the HARD state transitions.  So the result 
is that when I show a SQL query for all of the HARD state transitions (by 
searching in icinga_servicechecks table for state_type = 1, which is HARD 
states),  I see all of these HARD recovery "OK" states, even though there was 
never a HARD non-OK state.

This is confusing to the user.  Why does Icinga2 make the recovery a HARD OK 
state, if the problem was not a HARD state?  I end up with hundreds of HARD OK 
states, even though there was never a HARD non-OK state.  It seems unbalanced.  
The same thing happens in my notification that gets called - it records all of 
these hundreds of HARD OK states, even though there was never a problem to 
begin with.

Is there any way I can configure Icinga2 to NOT make the recovery a HARD state 
change unless the problem was a HARD problem to begin with?  I have searched 
for various config options (like setting "interval = 0" in the "apply 
Notification to Service...") but I'm not sure that is relevant.  But there are 
so many configuration options, that perhaps there is a way to achieve what I 
want.

I hope I am expressing this clearly enough.

Thank you,

Jude George

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to