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

Container logs can very large and should be compressed #231

Closed
yanokwa opened this issue Aug 25, 2021 · 1 comment · Fixed by #234 or #237
Closed

Container logs can very large and should be compressed #231

yanokwa opened this issue Aug 25, 2021 · 1 comment · Fixed by #234 or #237

Comments

@yanokwa
Copy link
Member

yanokwa commented Aug 25, 2021

Containers logs (particularly nginx and service) can be very large and take up a lot of space. Also, it isn't fast to docker logs container | grep foo them for issues.

We can't use logrotate inside the containers because they all report out on stdout/err, but it looks like we can configure the “local” logging driver and it does log-rotation by default and still works with docker logs, so we can do docker logs --since 10m <container_id>.

My bias is to do this for every container in the docker-compose.yml file.

@yanokwa
Copy link
Member Author

yanokwa commented Sep 1, 2021

I looked at the logs on server and here's what is taking up space since the server started in July 2021 (roughly 3 months) and has 550k submissions

nginx 637M
service  14M
enketo  27K
postgres  56K
pyxform  45K
redis  54K
redis 118K
smtp 1.2K

Given this, I propose we only deal with logging for nginx and service.

@matthew-white matthew-white linked a pull request Sep 22, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant