Alarms with a Path Outage are not cleared automatically

Description

If you have suppressed outages with a critical path defined, the node alarms affected by the outage of the critical node are not cleared automatically if they come back online. You have to acknowledge these alarms manually.

Acceptance / Success Criteria

None

Attachments

3

Lucidchart Diagrams

Activity

Show:

Ronny Trommer November 16, 2016 at 7:38 AM

This issue seems to be similar than ,

Cyrille Bollu February 5, 2016 at 3:45 AM

Hello,

I've just uploaded a view of a node's events in case of path outage.

We can see in there the nodeDown event (updated with pah outage information) at 21h52'25'' (event 14228943).

Then, at 21h52'32'', a "uei.opennms.org/nodes/pathOutage" event is sent (event 14228944).

Then, at 21h54'54'', OpenNMS sees the node up again, and sent the corresponding nodeUp event (event 14229097).

But, there's never a kind of "clearPathOutage" event to clear event 14228944.

The thing is, in OpenNMS, there's no event defined to clear "uei.opennms.org/nodes/pathOutage" events.

The question is: Is this "uei.opennms.org/nodes/pathOutage" event even needed when the corresponding nodeDown event has already been updated to contain path outage information?

Cyrille

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created November 23, 2015 at 10:21 AM
Updated September 21, 2021 at 6:24 PM