We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do we need to implement logrotate for the go-audit.log file? Or is there a way to add logrotate in the go-audit.yaml file?
In auditd you can set logrotate in the auditd.conf file just wondering if there is something similar in go-audit.
max_log_file = 8 num_logs = 5 max_log_file_action = ROTATE
go-audit version: 1 OS version(s): Centos 8
go-audit
go-audit.log does not grow to big in size.
e.g. What actually happened
e.g. Logs, screenshots, screencast, sample project, funny gif, etc.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Do we need to implement logrotate for the go-audit.log file? Or is there a way to add logrotate in the go-audit.yaml file?
In auditd you can set logrotate in the auditd.conf file just wondering if there is something similar in go-audit.
max_log_file = 8
num_logs = 5
max_log_file_action = ROTATE
Reproducible in:
go-audit
version: 1OS version(s): Centos 8
Steps to reproduce:
Expected result:
go-audit.log does not grow to big in size.
Actual result:
Attachments:
The text was updated successfully, but these errors were encountered: