From baed8c2450cdcd6fbed9dd4aa4eaa859363806fd Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 5 Jan 2025 03:22:18 -0500 Subject: [PATCH] Update docs/configuring-playbook-bridge-mautrix-bridges.md: reflect the review See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3913#discussion_r1903215741 Co-authored-by: Slavi Pantaleev Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-bridges.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md index a38287985..24576ab94 100644 --- a/docs/configuring-playbook-bridge-mautrix-bridges.md +++ b/docs/configuring-playbook-bridge-mautrix-bridges.md @@ -116,12 +116,12 @@ matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME" To specify the logging level, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml -matrix_mautrix_SERVICENAME_logging_level: WARN +matrix_mautrix_SERVICENAME_logging_level: warn ``` -Replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL. +Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`. -If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful. +If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful. ### Extending the configuration