Architecture #24963
openPersist compliance in base to know last state for a long time
Description
We need to persist compliance in base to be able to:
- restore the last known state when rudder start up
- more finely control persistance expiration by node.
More saillantly, we want to be able to address the case:
- a node compliance should be kept for several days when a node is not answering (typically: laptop when people go on hollidays),
- we want to avoid keeping run reports for more than a day for storage reason
That case is not possible without persistence in base.
Today, we compute compliance from expected reports and last run reports, always. If we don't have run reports, we don't have compliance.
Updated by François ARMAND 6 months ago
- Related to Architecture #24876: Add a compliance-by-feature logic and save compliance in base added
Updated by François ARMAND 6 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 6 months ago
- Related to User story #4234: Add online|offline check before calculating status added
Updated by François ARMAND 6 months ago
- Related to Architecture #24964: Remove unused tables about compliance and eventlogs added
Updated by Vincent MEMBRÉ 4 months ago
- Target version changed from 8.2.0~alpha1 to 8.2.0~beta1
Updated by François ARMAND 3 months ago
Work in progess here: https://github.com/fanf/rudder/commit/4b948032dcd05758176d9fbeb7df91a29e3cebf4
Updated by Vincent MEMBRÉ 3 months ago
- Target version changed from 8.2.0~beta1 to 8.2.0~rc1
Updated by François ARMAND about 1 month ago
- Status changed from In progress to Pending release
This was completed in Rudder 8.2.0.beta2
Updated by François ARMAND about 1 month ago
- Related to Enhancement #25649: Node with kept compliance should have the clock icon in node list added
Updated by François ARMAND about 1 month ago
- Related to Enhancement #25572: We need an icon and recognizable message style for node with expired maintained compliance added
Updated by François ARMAND about 1 month ago
- Related to Bug #25650: Node in with no reports, pending and keep compliance lead to computation loop added
Updated by Vincent MEMBRÉ about 1 month ago
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.