Skip to content
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

Log rotation mechanism #3066

Closed
wey-gu opened this issue Oct 14, 2021 · 1 comment · Fixed by #3541
Closed

Log rotation mechanism #3066

wey-gu opened this issue Oct 14, 2021 · 1 comment · Fixed by #3541
Assignees
Labels
type/feature req Type: feature request
Milestone

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Oct 14, 2021

Is your feature request related to a problem? Please describe.
As titled, some users complained about log Explosion(error LOG) led disk full.

And log rotation integration via syslog(or others) in RPM/DEB package seems to be a good feature.

Describe the solution you'd like
Log to be placed in /var/log or equivalent path could help(need to consider multiple instances co-existing in the same OS situation)? Or RPM/DEB script to integrate with syslog?

For the case of docker-compose/swarm/k8s, things are different yet still need to be considered.

Describe alternatives you've considered
N/A

Additional context
from WeChat Group

@wey-gu wey-gu added the type/feature req Type: feature request label Oct 14, 2021
@wey-gu
Copy link
Contributor Author

wey-gu commented Oct 14, 2021

crontab to delete based on time brings efforts from the user side, and it could only address the case log is growing at the normal rate(cannot save the user from the explosion case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants