You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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)
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
The text was updated successfully, but these errors were encountered: