Bug 55923 – Logrotate configuration for config-registry.replog questionable

Bug 55923 - Logrotate configuration for config-registry.replog questionable


Summary:	Logrotate configuration for config-registry.replog questionable

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	logrotate
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-03-30 11:39 CEST by Dirk Schnick
Modified:	2023-03-30 11:39 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Schnick 2023-03-30 11:39:00 CEST

The logrotate of config-registry.replog in default installation says: rotate 12 -> weekly
So you only hold 12 weeks of UCR var changes. This logfile do not need extensive diskspace, but can be very helpful in f.e. support cases, as you can verify (with a long term configuration) how a UCR was configured in the past.

I strumbled several times over missing historical UCR informations in the last weeks.

No big deal, no heavy pain, but from my point of view a better practise to keep that logfile a (much) longer time and within an enhancement of the default config of UCS systems.
You may close the bug with won't fix but I wanted to have it mentioned