Update default notification configuration to leverage alarm autoacknowledgements
Description
Acceptance / Success Criteria
Attachments
Lucidchart Diagrams
Activity
Jesse White September 25, 2019 at 3:47 PM
This was reverted in release-25.0.0 due to the problem noted above. We can revisit this once we have more time to investigate.
Jesse White September 25, 2019 at 1:55 PM
With this change in place, we encountered an issue where Notifd was blocked with the following stack and did not recover:
Running
Revealed:
Also:
Ronny Trommer September 18, 2019 at 2:57 PM
Merged to release-25.0.0
Ronny Trommer September 13, 2019 at 2:47 PM
PR to review: https://github.com/OpenNMS/opennms/pull/2699
Alejandro Galue July 31, 2019 at 4:39 PM
It should be something like this:
Any event that has alarm data can be used with auto-acknowledge-alarm, and because all the default events on this file follow this pattern, all of them can be replaced with a single entry, besides the benefit of having the functionality for every single event with alarm-data that has a notification for the "trigger" problem.
The way that works is based on the reduction-key/clear-key matching. I know this functionality has been changed recently, so to be honest, I'm not 100% sure if this feature (which exists since Horizon 14) still works on very recent versions like H24 or the upcoming H25.
I'm not sure if this is too late, but I just learned about the ability to map the notifd autoacknowledgement to alarms. I would like to replace the default notifd configuration with the attached.
Possible?
If not, please lower the Priority.