Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #11320] Volatile transitions from HARD NOT-OK->NOT-OK do not trigger notifications #4006
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11320
Created by dmpcore on 2016-03-07 08:59:09 +00:00
This ticket comes from monitoring-portal:
I'm trying to configure one volatile service so it notifies always that the check returns a CRITICAL state, and not by interval. But it isn't working properly.
I attach the configuration file and the debug file with one test I've made (testing several cases):
And this de de runtime object configuration:
dnsmichi says it could be a bug with NOT-OK -> NOT-OK transitions in volatile objects.
2016-03-11 12:19:03 +00:00 by mfriedrich 3e050bd
2016-03-11 14:56:43 +00:00 by mfriedrich 7ad7e28
Updated by mfriedrich on 2016-03-09 10:57:38 +00:00
I'll look into that, thanks for the report.
Updated by mfriedrich on 2016-03-11 12:20:12 +00:00
Found it. The current code only sends notifications for HARD state changes meaning a transition from SOFT to HARD. The documentation for volatile services says that notifications happen for each new check results in a HARD state.
Re-order the send notification a bit while at it.