-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No logging or compaction enabled for logs in snap internal /var/log/ folders #653
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5703.
|
Hi, @ethanmye-rs, at the moment the charm configures Postgresql to write a log every minute for every day of the week which will be overwritten at the turn of the week. So the charm will keep only 7 days worth of logs. Size of the logs will be variable, since the rotation is based on time, and there will always be around ~10k files, one for every minute of the week, |
Thanks Dragomir for the context. Would you consider making this configurable at the charm/snap level? While this might be a reasonable config for some workloads, it is not ideal for others. |
@dragomirp is it possible to re-use / integrate with logrotated subordinate charm? We typically use it for Openstack charms inside |
Hi, @ethanmye-rs and @gustavosr98! For that topic, I believe it's important to involve our PM here. @7annaba3l, what's your thought about that? |
Steps to reproduce
Expected behavior
I expect the internal /var/log/ folder to start compacting old logs and eventually rotating them. I would like charm or snap level config knobs to alter this behavior (ie rotate logs after x days, keep logging directory under x GB, etc).
Actual behavior
files just build up in var/log/.
Versions
Operating system: 22.04.5 LTS
Juju CLI: 3.5.4
Juju agent: 3.5.0
Charm revision: 429
LXD: 5.0.3
The text was updated successfully, but these errors were encountered: