Option to ignore resolved alerts in queue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Wishlist
|
Thomas Adamcik | ||
3.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In NAV-v2 there was an option for not getting sms-alerts (for instance
boxDown) if they happened during some interval (more specifically the
night) but get an alert if the issue was not fixed at the end of the
interval (typically the morning). If the issue was fixed during the
interval in which you did not get alerts, you would get no alert at the end
of the interval.
This option is highly sought after in NAV-v3 because it enables the network
personell on duty to know if something needs to be done at the start of the
day.
This may be done by creating a new queueing type only used in conjunction
with sms-alerts in the Alertprofiles. When used this should mirror the
functionality explained in the beginning of this message.
[http://
Changed in nav: | |
importance: | Medium → Wishlist |
Changed in nav: | |
assignee: | nobody → adamcik |
Changed in nav: | |
status: | New → Triaged |
Changed in nav: | |
status: | Triaged → In Progress |
Changed in nav: | |
status: | Fix Committed → Fix Released |
http:// metanav. uninett. no/hg/default/ rev/2c3a671f62c a adds an alerthistid foreign key to the alertq. Once the django models _and_ eventEngine have been updated to use and populate this field, alertengine can start checking the subscriptions ignore_ closed_ alerts.