After a webapp downtime, no compliance is visible for a long time
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 2 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