Skip to:

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

Acknowledged alarm for an ongoing outage is not reopening

Description

If you work with alarms and you get an alarm for example an nodeDown, interfaceDown or nodeLostService and an user acknowledged this alarm for - the reason he handles this outage - you won't get any alarm from this node again. The reason is the reduction key which is used to create an alarm. Any new event matching the reduction key just counted on the already acknowledged alarm and will never show up again as a new instance of the alarm.

Working branch: https://github.com/OpenNMS/opennms/tree/NMS-8011

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

David Hustace July 22, 2016 at 8:58 AM

I think that I misunderstood Cyrille's comment. But I do understand his comment regarding manually cleared events.

Having said that, this is one of the projects that I plan to begin addressing this year at DevJam. We just need a better design and more configurable process for handling the state of Faults managed by the NMS.

David Hustace July 22, 2016 at 8:54 AM
Edited

I don't know when the behavior began that events matching acknowledged alarms are not being reduced into the existing alarm but this was the design and should still be that way since the reductionKey has nothing to do with acknowledgment state.

Ronny Trommer May 13, 2016 at 4:25 AM

I agree with you. That's the reason I opened this issue, the default OpenNMS workflow is in my opinion not really useable.

Cyrille Bollu January 19, 2016 at 6:54 AM

Hi Ronny,

I don't understand why OpenNMS should duplicate acknowledged alarms.

In my opinion, when I've acknowledged an alarm, that means I know there's a problem and there's no need for OpenNMS to create new alarms related to this problem.

Don't you agree?

Cyrille Bollu January 19, 2016 at 6:51 AM

Not that easy David: Your solution doesn't work for manually cleared events.

But maybe it's easy to hack the code to add this ":cleared" part when manually clearing an event

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Parent

PagerDuty

Created December 2, 2015 at 10:11 AM
Updated July 26, 2023 at 2:15 PM