Actions
Bug #19064
open
After a webapp downtime, no compliance is visible for a long time
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
After a webapp unavailability, when it is restarted, it will process reports in the order of arrival, which means it will process all previous reports, before being able to compute current compliance.
There is no indication in the interface or the logs, so the server just looks broken.
Updated by François ARMAND over 3 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to First impressions of Rudder
- Effort required set to Very Small
- Priority changed from 0 to 109
Elaad, can you assess the complexity of this one?
It could be one more check in the health check.
The heuristic should be just to call LastProcessedReportRepositoryImpl and check that the date returned by `getExecutionStatus` is not older than 2 times the scheduling interval in FindNewReportsExecution
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.5 to 6.2.6
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.6 to 6.2.7
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.7 to 6.2.8
- Priority changed from 109 to 108
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.8 to 6.2.9
- Priority changed from 108 to 105
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.9 to 6.2.10
- Priority changed from 105 to 104
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.10 to 6.2.11
- Priority changed from 104 to 102
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.2.11 to 6.2.12
- Priority changed from 102 to 98
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.2.12 to 6.2.13
- Priority changed from 98 to 96
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.13 to 6.2.14
- Priority changed from 96 to 91
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.14 to 6.2.15
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.15 to 6.2.16
Updated by Alexis Mousset over 2 years ago
- Target version changed from 6.2.16 to 6.2.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.17 to 997
- Priority changed from 91 to 0
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 997 to 6.2.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.18 to 6.2.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.19 to 6.2.20
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.2.20 to old 6.2 issues to relocate
Updated by Alexis Mousset over 1 year ago
- Target version changed from old 6.2 issues to relocate to 7.2.11
- Regression set to No
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.11 to 1046
Updated by Alexis Mousset about 1 year ago
- Target version changed from 1046 to 7.3.8
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.9 to 7.3.10
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.10 to 7.3.11
Updated by Vincent MEMBRÉ 11 months ago
- Target version changed from 7.3.11 to 7.3.12
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.12 to 7.3.13
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.13 to 7.3.14
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 7.3.14 to 7.3.15
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 7.3.15 to 7.3.16
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 7.3.16 to 7.3.17
Actions