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

[Questions] Why envoy access log not support size limit & rotation ? And is there any good practice for this access log & envoy binary debug log ? #33767

Closed
wufanqqfsc opened this issue Apr 24, 2024 · 2 comments
Labels
area/access_log question Questions that are neither investigations, bugs, nor enhancements

Comments

@wufanqqfsc
Copy link

Seems there is no such log file size limit & rotation configurations supported by Envoy ?

Is there any good practice for these log file collection ?

@wufanqqfsc wufanqqfsc added the triage Issue requires triage label Apr 24, 2024
@wbpcode
Copy link
Member

wbpcode commented Apr 26, 2024

logrotate is good choice for this requirement. You can set the postrotate in the logrotate config to

kill -USR1 `pgrep envoy`

Then the logrotate will send a signal to envoy to force envoy to reopen the log file after logrotate moved the old one.

@wbpcode wbpcode added question Questions that are neither investigations, bugs, nor enhancements area/access_log and removed triage Issue requires triage labels Apr 26, 2024
@wufanqqfsc
Copy link
Author

logrotate

Thanks very much @wbpcode ,this logrotate seems a good choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/access_log question Questions that are neither investigations, bugs, nor enhancements
Projects
None yet
Development

No branches or pull requests

2 participants