Bug #7165
closed
Dates of Alarms for Low availability are reset on each update
Added by Lequeux Olivier about 12 years ago.
Updated almost 12 years ago.
Description
Consequently Alarm Age is wrong !!!!
Files
I would like to also point possible problem with calculation of duration of alarm displayed in "Alarm age" column.
Test executed at 4:51 UTC
So in our nagios at 6:51 CEST
I checked at 8:41 CEST, and in dashboard alarm had 3h (while in my opinion had only 1h50m)
- Priority changed from High to Urgent
- Priority changed from Urgent to Immediate
- Status changed from Assigned to Resolved
- Target version set to 146
- Translation missing: en.field_release set to 2
- % Done changed from 0 to 100
- Target version deleted (
146)
Also available in: Atom
PDF