You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:49 +00:00 (in Redmine)
Icinga Version: 1.7.2
OS Version: Any
A service state is immediately HARD in case it's host is not UP. It doesn't matter whether the host is in a soft or hard state. In such a situation (happens all the time when a host goes down) last_hard_state is wrong and shows the current_hard_state instead of the last one.
I tried to simulate this with passive check results:
Given that:
Host 'host' is UP (hard state)
Service 'PING' is OK (hard state)
...I'm sending passive check results:
EXTERNAL COMMAND: PROCESS_HOST_CHECK_RESULT;host;1;Fake Host DOWN
EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;host;PING;2;Fake Service CRIT
I check the statehistory in the IDO:
+------+-------+------------+-----------------+--------------------+
| type | state | last_state | last_hard_state | output |
+------+-------+------------+-----------------+--------------------+
| hard | 2 | 0 | 2 | Fake Service CRIIT |
| hard | 1 | 0 | 0 | Fake Host DOWN |
And the current state:
icinga_servicestatus:
output: Fake Service UNKNOWN
current_state: 2
last_hard_state: 2
Expected last_hard_state would be 0. It behaves correct in case the host is NOT down and the service regularly reaches it's max_check_attempts. Please note that while showing IDO data in my believes this is a core issue.
IMHO core behaviour is clearly wrong here. This has severe impacts on availability reports and leads to ugly workarounds.
Regards,
Thomas
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/4734
Created by tgelf on 2013-09-24 12:27:36 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:17:49 +00:00 (in Redmine)
A service state is immediately HARD in case it's host is not UP. It doesn't matter whether the host is in a soft or hard state. In such a situation (happens all the time when a host goes down) last_hard_state is wrong and shows the current_hard_state instead of the last one.
I tried to simulate this with passive check results:
Given that:
...I'm sending passive check results:
I check the statehistory in the IDO:
And the current state:
Expected last_hard_state would be 0. It behaves correct in case the host is NOT down and the service regularly reaches it's max_check_attempts. Please note that while showing IDO data in my believes this is a core issue.
IMHO core behaviour is clearly wrong here. This has severe impacts on availability reports and leads to ugly workarounds.
Regards,
Thomas
The text was updated successfully, but these errors were encountered: