Project

General

Profile

Actions
Copy link

Bug #15802

closed

Clean up reports with log_* types more than once a day

Added by François ARMAND about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Performance and scalability
Target version:
5.0.14
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:

Description

With Rudder 5.1, we will store much more reports with log levels than we do today. It will make the base groth much more quickly than today.
Moreover, we need to clean it often: log reports don't have any usage bug for "technical log" and will only be used for immediate display.

Moreover, we should do that in 5.0 too, because even with current set-up, log level takes around 15% of report DB size for nothing.

We should keep around 2x max run time log and delete others.

Subtasks 1 (0 open — 1 closed)

Bug #15890: Batch which deletes log reports displays an error when default run interval is not definedReleasedNicolas CHARLESActions

Related issues 3 (0 open — 3 closed)

Related to Rudder - Bug #15849: Missing a fork for clean report info batchReleasedVincent MEMBRÉActions
Related to Rudder - Bug #15888: Batch which cleans log reports should not start if LDAP is unavailableResolvedFrançois ARMANDActions
Related to Rudder - Bug #15974: Document specific purging configuration for log_* reportsReleasedAlexis MoussetActions
Actions
Copy link

Also available in: Atom PDF