There is a parameter to require multiple positive tests before marking a
service OK, so you can enable a *SOFT* recovery if you want ;)
It’s really a config. If the number of tests to fail/succeed > 1 then you will
have SOFT states of either one.
On Sep 22, 2015, at 2:17 PM, George, Jude <jude.geo...@bluecoat.com> wrote:
> I have discovered a solution in SQL to only retrieve the HARD state changes.
> In the query of the icinga_statehistory table, select state transitions where
> state_type = 1 ("HARD") AND last_state = 1 ("HARD").
> This seems to have the effect that I desire -- which is to exclude all the
> HARD "OK" state changes which occur after a SOFT non-OK state, and thus only
> show the HARD non-OK states along with the HARD OK state changes that occur
> after a HARD non-OK state.
>
> Best regards,
> Jude George
>
>> From: George, Jude
>> Sent: Tuesday, September 22, 2015 1:31 PM
>> To: 'icinga-users@lists.icinga.org'
>> Subject: Don't want to see HARD recovery states that follow a SOFT error
>> state
>>
> [ removed ]
>
>> 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.
>
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
--
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
