AFAIK, we currently do no log rotation outside of what systemd may provide, and I don't think we have a unified policy on log rotation. I think we should do the following:
Document and specify what our log rotation policies should be (time-based? size-based? both? is it component-dependent or system-wide?)
Add appropriate log rotation policies to all default components
Make it easy add log rotation to a recipe that doesn't currently have it ("inherit logrotate" ?)
To start working on this, first we should discuss these issues and come to an agreement about the right rotation policies, and which software we want to use to rotate logs. After that, we can assign work and figure out implementation.
Environment
None
Activity
Show:
Martin Kelly May 31, 2017 at 5:24 AM
Resolving in favor of , which addresses a more general issue (this is a simple case of a larger issue that we need to solve).
Major
AFAIK, we currently do no log rotation outside of what systemd may provide, and I don't think we have a unified policy on log rotation. I think we should do the following:
Document and specify what our log rotation policies should be (time-based? size-based? both? is it component-dependent or system-wide?)
Add appropriate log rotation policies to all default components
Make it easy add log rotation to a recipe that doesn't currently have it ("inherit logrotate" ?)
To start working on this, first we should discuss these issues and come to an agreement about the right rotation policies, and which software we want to use to rotate logs. After that, we can assign work and figure out implementation.