Project

General

Profile

Actions
Copy link

Bug #7165

closed

Dates of Alarms for Low availability are reset on each update

Added by Lequeux Olivier almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Immediate
Assigned To:
L'Orphelin Cyril
Category:
-
Start date:
05/16/2014
Due date:
% Done:

100%

Estimated time:
Story points-Velocity based estimate-Release3.0.4Release relationshipAuto

Description

Consequently Alarm Age is wrong !!!!

Files

Download all files
Zrzut ekranu z 2014-07-01 08_41_52.png (167 KB) Zrzut ekranu z 2014-07-01 08_41_52.png Szymocha Tadeusz, 07/01/2014 08:45 AM
Zrzut ekranu z 2014-07-01 08_45_47.png (127 KB) Zrzut ekranu z 2014-07-01 08_45_47.png Szymocha Tadeusz, 07/01/2014 08:46 AM
Actions
Copy link
 #1

Updated by Lequeux Olivier almost 10 years ago

Actions
Copy link
 #2

Updated by Szymocha Tadeusz almost 10 years ago

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)

Actions
Copy link
 #3

Updated by Lequeux Olivier almost 10 years ago

  • Priority changed from High to Urgent
Actions
Copy link
 #4

Updated by L'Orphelin Cyril almost 10 years ago

  • Priority changed from Urgent to Immediate
Actions
Copy link
 #5

Updated by L'Orphelin Cyril almost 10 years ago

  • Status changed from Assigned to Resolved
Actions
Copy link
 #6

Updated by L'Orphelin Cyril almost 10 years ago

  • Target version set to 146
Actions
Copy link
 #7

Updated by L'Orphelin Cyril almost 10 years ago

  • Release set to 3.0.4
Actions
Copy link
 #8

Updated by L'Orphelin Cyril almost 10 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #9

Updated by Lequeux Olivier over 9 years ago

  • Target version deleted (146)
Actions
Copy link

Also available in: Atom PDF