No alert information when alerttype is missing from alertmsg.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Morten Brekkevold |
Bug Description
When an event is posted, whose corresponding eventtype or alerttype is not defined in alertmsg.conf, no alert message will be posted to the alertqmsg table. The new AlertEngine in NAV 3.5 will never dispatch such an alert to a user. The old alert engine would dispatch a more or less empty alert.
The event engine should fall back to create an alert message which contains as much information as possible about the alert in question, so that a recipient of the alert at least has a chance to decipher what the alert is all about.
In Email/Jabber alerts, the eventtype, alerttype and alert variables could be dumped as they are into the alert text. For SMS, a reference to the netbox and the event/alerttype should be short enough.
Changed in nav: | |
assignee: | nobody → mvold |
importance: | Undecided → Medium |
milestone: | none → v3.5.3 |
status: | New → Confirmed |
Changed in nav: | |
status: | Confirmed → In Progress |
Changed in nav: | |
status: | Fix Committed → Fix Released |
Fix committed and pushed to series/3.5.x: http:// metanav. uninett. no/hg/series/ 3.5.x/rev/ 5cc2124f3f53