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

Document SYNAPSE_LOG_LEVEL to configure logging severity in Docker #9934

Closed
1 task
MadLittleMods opened this issue May 6, 2021 · 2 comments
Closed
1 task
Labels
A-Docker Docker images, or making it easier to run Synapse in a container. A-Docs things relating to the documentation P3 (OBSOLETE: use S- labels.) Approved backlog: not yet scheduled, will accept patches T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@MadLittleMods
Copy link
Contributor

Description:

SYNAPSE_LOG_LEVEL is used in docker/conf/log.config to set the logger severity level but is not documented anywhere.

The log severity can also be overriden by setting a log_config in homeserver.yaml (SYNAPSE_CONFIG_PATH)

SYNAPSE_CONFIG_PATH: path to the file to be generated. Defaults to <SYNAPSE_CONFIG_DIR>/homeserver.yaml.

Dev notes

Alternative

Remove this config altogether in favor of having to specify a log_config in homeserver.yaml

Definition of done

We have a nice list of variables on https://hub.docker.com/r/matrixdotorg/synapse which this would fit nicely in.

@babolivier babolivier added P3 (OBSOLETE: use S- labels.) Approved backlog: not yet scheduled, will accept patches T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. labels May 10, 2021
@MadLittleMods
Copy link
Contributor Author

Related MR that documented SYNAPSE_TEST_LOG_LEVEL, #10148

@richvdh richvdh added A-Docker Docker images, or making it easier to run Synapse in a container. A-Docs things relating to the documentation labels Sep 10, 2021
@MadLittleMods
Copy link
Contributor Author

MadLittleMods commented Jul 22, 2022

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-Docs things relating to the documentation P3 (OBSOLETE: use S- labels.) Approved backlog: not yet scheduled, will accept patches T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

3 participants