浏览代码

Update docs/configuring-playbook-alertmanager-receiver.md: remove duplicated instruction

Usage of matrix_alertmanager_receiver_config_matrix_room_mapping is decribed below in the "Adjusting the playbook configuration" much more nicely.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/3881/head
Suguru Hirahara 1年前
父节点
当前提交
7081124237
找不到此签名对应的密钥 GPG 密钥 ID: E4F9743DAB4B7B75
共有 1 个文件被更改,包括 0 次插入2 次删除
  1. +0
    -2
      docs/configuring-playbook-alertmanager-receiver.md

+ 0
- 2
docs/configuring-playbook-alertmanager-receiver.md 查看文件

@@ -34,8 +34,6 @@ For each new room you would like the bot to deliver alerts to, invite the bot to


Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out. Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out.


You may optionally adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID. It provides cleaner `/alert/` URLs.

## Adjusting the playbook configuration ## Adjusting the playbook configuration


Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#get-an-access-token). Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#get-an-access-token).


正在加载...
取消
保存