If the system date/time is set forward by a few days, Icinga2 will
continue polling and we'll see the last-check-time and state of the
objects updated accordingly -- the timestamps will be at the new, future
time. However, if the system date/time is then restored (back) to its
original time, Icing
The Icinga 1 documentation gives a clear explanation that a transition from a
non-OK to an OK state will be a HARD recovery in a single polling interval (the
max_check_attempts and retry_interval are not used).
http://docs.icinga.org/latest/en/statetypes.html
The Icinga2 documentation regarding
Just a follow-up to this earlier question I had posed. My prior solution was
incorrect.
I have discovered a way in SQL to ignore subsequent HARD recoveries into an
"OK" state that follow any SOFT non-OK states.
The PostgreSQL query (on the icinga_statehistory table) is as follows:
state_type ==
de 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
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
How can I clear the contents of the Icinga2 database? I want to revert its
contents to be like when it was freshly installed.
I found no reference in the documentation or online forums to how to do this.
Thank you,
Jude George
Blue Coat Systems
___
ic
How can I peruse a history of past check results? Not past state changes, but
the actual check values, even if they did not result in a state change.
For example, if the past 20 service checks for some object resulted in "OK"
status, I still want to see the checker output for those past 20 check
Icinga2 has a "check now" link-button which appears in the Service detail
information panel in the icingaweb2 GUI. This forces the next check to run
immediately (or within the next few seconds) rather than waiting for the next
regularly scheduled check time.
How do I perform this function with
