Project

General

Profile

Actions

Bug #15802

closed

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

Added by François ARMAND over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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 open1 closed)

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

Related issues

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 unavailableNewFrançois ARMANDActions
Related to Rudder - Bug #15974: Document specific purging configuration for log_* reportsReleasedAlexis MOUSSETActions
Actions #1

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/2489
Actions #3

Updated by François ARMAND over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by François ARMAND over 1 year ago

  • Related to Bug #15849: Missing a fork for clean report info batch added
Actions #7

Updated by François ARMAND over 1 year ago

  • Related to Bug #15890: Batch which deletes log reports displays an error when default run interval is not defined added
Actions #8

Updated by François ARMAND over 1 year ago

  • Related to deleted (Bug #15890: Batch which deletes log reports displays an error when default run interval is not defined)
Actions #11

Updated by Alexis MOUSSET over 1 year ago

  • Subject changed from Clean up report with level log info more than once a day to Clean up reports with log_* types more than once a day
Actions #12

Updated by François ARMAND over 1 year ago

  • Related to Bug #15888: Batch which cleans log reports should not start if LDAP is unavailable added
Actions #13

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.14 which was released today.

Actions #14

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #15974: Document specific purging configuration for log_* reports added
Actions

Also available in: Atom PDF