Просмотр исходного кода

Update files for matrix-bridge-hookshot: sort logging levels

Based on docs/configuring-playbook-alertmanager-receiver.md

We can re-sort the levels it if is found out that debug should be placed at the first.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/3998/head
Suguru Hirahara 1 год назад
Родитель
Сommit
e8213768a5
Не найден GPG ключ соответствующий данной подписи Идентификатор GPG ключа: E4F9743DAB4B7B75
2 измененных файлов: 2 добавлений и 2 удалений
  1. +1
    -1
      docs/configuring-playbook-bridge-hookshot.md
  2. +1
    -1
      roles/custom/matrix-bridge-hookshot/defaults/main.yml

+ 1
- 1
docs/configuring-playbook-bridge-hookshot.md Просмотреть файл

@@ -153,6 +153,6 @@ As with all other services, you can find the logs in [systemd-journald](https://
The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:

```yaml
# Valid values: debug, info, warn, error
# Valid values: error, warn, info, debug
matrix_hookshot_logging_level: debug
```

+ 1
- 1
roles/custom/matrix-bridge-hookshot/defaults/main.yml Просмотреть файл

@@ -183,7 +183,7 @@ matrix_hookshot_provisioning_internal: "/v1"
matrix_hookshot_provisioning_hostname: "{{ matrix_hookshot_public_hostname }}"
matrix_hookshot_provisioning_endpoint: "{{ matrix_hookshot_public_endpoint }}{{ matrix_hookshot_provisioning_internal }}"

# Valid logging levels are: debug, info, warn, error
# Valid values: error, warn, info, debug
matrix_hookshot_logging_level: warn

matrix_hookshot_widgets_enabled: true


Загрузка…
Отмена
Сохранить