Duplicate
Details
Assignee
OpenNMS Bug Mailing ListOpenNMS Bug Mailing ListReporter
Tarus BalogTarus BalogComponents
Fix versions
Affects versions
Priority
Minor
Details
Details
Assignee
OpenNMS Bug Mailing List
OpenNMS Bug Mailing ListReporter
Tarus Balog
Tarus BalogComponents
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created April 4, 2007 at 10:56 AM
Updated January 27, 2017 at 4:32 PM
Resolved September 3, 2010 at 6:02 PM
Here is a scenario:
A destination path is created in the follow fashion. A group of users are notified of a problem. Five
minutes later an escalation notifies those same people (if the notice isn't acknowledged or resolved). Five
minutes after that the escalation is repeated.
If all three notices are sent, when the problem is actually resolved a total of three "resolved" messages are
sent, one for each notice. There should be some way to restrict this to just one resolved message per
person.