Auto-acknowledged *up* notices do not reach users notified with *down* messages

Description

When clear="true" in the <auto-acknowledge> tag (notifd-configuration.xml) the
up notice that matches a previous down message and acknowledges it is not
propagated through the notification path up to the targets that have received
the first notice.

On the other hand, if clear="false" the first message is ack'ed but the second
message is not cleared, and is propagated up the escalation ladder if not
acknowleged by hand. So, in this case targets that did not receive the down
message receive up message...

As Bill Felling stated on the discuss list:
> The ideal behavior from my point of view would be that when the "up" notice
> comes in, if clear="true" is set it clears the down notice, is sent to as
> many people as received the "down" notice, and then clears itself.

I am not sure which of all the possible situation are the most usefull (or
needed at all), but I agree with Bill's "ideal behaviour".

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Benjamin Reed November 2, 2010 at 10:36 PM

just doing some cleanup

Former user January 19, 2005 at 11:42 AM

Okay. I should have marked this fixed last week but now it is finally in. This
should now be fixed in head as of 1/18/2004. Please reopen this or let me know
if you have any other troubles with it.

The Poller and outaged have been rewritten in order to facilitate this so that
any down event that gets sent will always have its corresponding up event sent
(see )

Hope this makes things simple for y'all

Matt Brozowski

David Hustace December 9, 2004 at 10:35 PM

Writing JUnit test cases now. Should be fixed early next week.

Craig Miskell July 15, 2004 at 3:32 PM

  •  

    •  

      • has been marked as a duplicate of this bug. ***

Craig Miskell June 3, 2004 at 11:40 PM

Dammit - hit the wrong button and submitted to quickly. THis is a patch
against source 1.1.2 - it will probably apply cleanly against the latest CVS -
it's not a whole pile of radical changes, just some new chunks of code (some
new methods, a snippet in one method, and a single line change in another).

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created April 9, 2003 at 6:59 AM
Updated February 10, 2011 at 2:54 PM
Resolved November 2, 2010 at 10:36 PM