Daily alert queue is sent when timeperiod changes
Bug #258309 reported by
Morten Brekkevold
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Won't Fix
|
Medium
|
Thomas Adamcik | ||
Bug Description
This report comes from NTNU.
When a user sets up his alert profile with daily queuing for a given
equipment group, the alerts stored in the daily queue are sent as soon as
the profile switches to the next time period. I.e. no different than the
regular "queue until time period changes" option.
[http://
Revision history for this message
| Thomas Adamcik (adamcik) wrote | #1 |
Revision history for this message
| Thomas Adamcik (adamcik) wrote | #2 |
| Changed in nav: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
After having looked at this bug during the summer I believe this bug is caused by poor DB design in the alertengine system. The following example is an attempt at explaining what I think happens (if someone can confirm this for me please post a reply):
Due to the fact that queued messages are stored with a foreign key to the alarmaddress that should recieve the alert we can't be sure which queue type should be used we simply have to pick one that is connected to the address.
So if you are experiencing this problem try using your alarmaddress for one and _only_ one subscribtion, this will most likely allow you to avoid this problem. A proper fix for this (slight redesign of the db and rewrite of alertengine) will be available in 3.5.