Project

General

Profile

Actions

Architecture #24963

open

Persist compliance in base to know last state for a long time

Added by François ARMAND about 2 months ago. Updated about 9 hours ago.

Status:
In progress
Priority:
N/A
Category:
Architecture - evolution
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

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.


Subtasks 6 (0 open6 closed)

Architecture #25038: Switch service related to compliance persistance from box to IOResultReleasedClark ANDRIANASOLOActions
Architecture #25057: There is now a loop in initializationReleasedVincent MEMBRÉActions
Architecture #25087: Remove unexpected interpretation choice for vars because it's not meaningful anymoreReleasedClark ANDRIANASOLOActions
Architecture #25088: Remove unused methods in ReportingServiceReleasedClark ANDRIANASOLOActions
Architecture #25092: Refactor CachedReportingService to make persistance simplerReleasedClark ANDRIANASOLOActions
User story #25120: Use node properties to decide how long compliance is validReleasedClark ANDRIANASOLOActions

Related issues 3 (1 open2 closed)

Related to Rudder - Architecture #24876: Add a compliance-by-feature logic and save compliance in baseReleasedVincent MEMBRÉActions
Related to Rudder - User story #4234: Add online|offline check before calculating statusNew2013-12-09Actions
Related to Rudder - Architecture #24964: Remove unused tables about compliance and eventlogsReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND about 2 months ago

  • Related to Architecture #24876: Add a compliance-by-feature logic and save compliance in base added
Actions #2

Updated by François ARMAND about 2 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #3

Updated by François ARMAND about 2 months ago

  • Related to User story #4234: Add online|offline check before calculating status added
Actions #4

Updated by François ARMAND about 2 months ago

Actions #5

Updated by François ARMAND about 1 month ago

  • Subtask #25038 added
Actions #6

Updated by François ARMAND 25 days ago

  • Subtask #25087 added
Actions #7

Updated by François ARMAND 25 days ago

  • Subtask #25088 added
Actions #8

Updated by François ARMAND 23 days ago

  • Subtask #25092 added
Actions #9

Updated by François ARMAND 16 days ago

  • Subtask #25120 added
Actions

Also available in: Atom PDF