Make sure all Dell traps/events have corresponding notifications
Description
Environment
All
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:

Robin Bowes June 7, 2011 at 6:50 AM
OK, then I suggest that the notifications configuration should be overhauled to use an include mechanism similar to the events configuration, ie. so groups of notifications can easily be included/excluded.
Does that require a separate enhancement request?

Jeff Gehlbach June 5, 2011 at 1:31 PM
It's impractical to create notification definitions for every event that OpenNMS can recognize. Your request would result in the addition of almost a thousand notification definitions:
$ grep '<uei' Dell*.events.xml | wc -l
931
Imagine for a moment that your enterprise uses no Dell whatsoever, but every time you install OpenNMS you have to remove all those unwanted definitions.
Won't fix.
Won't Fix
Details
Assignee
Jeff GehlbachJeff GehlbachReporter
Robin BowesRobin BowesComponents
Affects versions
Priority
Major
Details
Details
Assignee

Reporter

Components
Affects versions
Priority
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Created November 30, 2010 at 10:58 AM
Updated June 7, 2011 at 6:50 AM
Resolved June 5, 2011 at 1:31 PM
All traps/events listed in the Dell events files should have corresponding Notifications in notifications.xml, although they may be turned off by default