Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Investigate reducing INFO logging impact on docker #8023

Open
erikjohnston opened this issue Aug 3, 2020 · 0 comments
Open

Investigate reducing INFO logging impact on docker #8023

erikjohnston opened this issue Aug 3, 2020 · 0 comments
Labels
A-Docker Docker images, or making it easier to run Synapse in a container. A-Logging Synapse's logs (structured or otherwise). Not metrics. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@erikjohnston
Copy link
Member

The context here is that we'd like to change our default logging to a) not take up so much room and b) use less disk I/O. For installations where we write logs to the disk we can do things like use buffered logging (#8018) and/or keeping INFO logging for a shorter period of time (#8019). Unfortunately, for docker Synapse logs to stderr which is then picked up by the docker daemon, making it hard/impossible to do the same sort of things we did when writing to disk.

Some potential ideas:

  • Log WARN to stderr, INFO to a mounted volume
  • Investigate if we can fiddle with e.g. syslog to make it to the write thing and then document that, etc
@erikjohnston erikjohnston added the A-Logging Synapse's logs (structured or otherwise). Not metrics. label Aug 3, 2020
@reivilibre reivilibre added A-Docker Docker images, or making it easier to run Synapse in a container. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. labels May 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Docker Docker images, or making it easier to run Synapse in a container. A-Logging Synapse's logs (structured or otherwise). Not metrics. T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

2 participants