Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

The auto-acknowledge-alarm tag with no content doesn't work on notifd-configuration.xml

Description

Adding a single entry for 

<auto-acknowledge-alarm resolution-prefix="RESOLVED: "> in notifd-configuration.xml does not auto-acknowledge alarms with alarm data.  No matching "RESOLVED" notifications are ever sent.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White May 30, 2018 at 2:40 PM

Alejandro Galue May 8, 2018 at 4:22 PM

This feature works property on Meridian 2015 and Meridian 2016. Unfortunately, it is not working on Meridian 2017 and latest Horizon. Speaking of Horizon and considering that the feature works perfectly on Meridian 2016, I would say that it get broken on Horizon 18 or newer.

Usually, the auto-ack feature was designed to match certain fields of the events, in order to auto-magically sends a "resolved" notification when a "rearm event" comes in, assuming that Notifd has sent a notification for the "problem event.

The auto-acknowledge-alarm tag can replace the old implementation (even if both can be used simultaneously).

It only requires that the "clear key" of the "rearm event" (i.e. the one with alarm-type="2"), matches the "reduction-key" of the "trigger event" (i.e. the one with alarm-type="1"), which is pretty much the default when the events have "alarm-data".

If the tag has no content inside of it, it is assumed that ALL the alarms will have the auto-ack feature enabled (well, all that have a notification definition for the trigger event). In other words:

<notifd-configuration xmlns="http://xmlns.opennms.org/xsd/config/notifd" status="on" match-all="true"> <auto-acknowledge-alarm resolution-prefix="RESOLVED: "/> <queue> <queue-id>default</queue-id> <interval>20s</interval> <handler-class> <name>org.opennms.netmgt.notifd.DefaultQueueHandler</name> </handler-class> </queue> </notifd-configuration>

The above is a 100% equivalent of the default configuration, but allows you to use the feature for other events that have notifications like threhsolds, without touching notifications.xml.

Or, you can specify an explicit list of UEIs to be considered for clear-key/reduction-key matching:

<notifd-configuration xmlns="http://xmlns.opennms.org/xsd/config/notifd" status="on" match-all="true"> <auto-acknowledge-alarm resolution-prefix="RESOLVED: "> <uei>uei.opennms.org/nodes/nodeUp</uei> <uei>uei.opennms.org/nodes/interfaceUp</uei> <uei>uei.opennms.org/nodes/nodeRegainedService</uei> </auto-acknowledge-alarm> <queue> <queue-id>default</queue-id> <interval>20s</interval> <handler-class> <name>org.opennms.netmgt.notifd.DefaultQueueHandler</name> </handler-class> </queue> </notifd-configuration>
Fixed

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 8, 2018 at 2:49 PM
Updated May 30, 2018 at 2:40 PM
Resolved May 30, 2018 at 2:40 PM

Flag notifications