From 4e20b15cb9965436fa89acf3a3caff43a9a0c37d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Ca=C3=B1ete?= <2930882+juacker@users.noreply.github.com> Date: Fri, 17 Nov 2023 17:44:19 +0100 Subject: Update integrations/cloud-notifications/metadata.yaml Co-authored-by: Tasos Katsoulas <12612986+tkatsoulas@users.noreply.github.com> --- integrations/cloud-notifications/metadata.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integrations/cloud-notifications/metadata.yaml b/integrations/cloud-notifications/metadata.yaml index 6d601daf16..c033172427 100644 --- a/integrations/cloud-notifications/metadata.yaml +++ b/integrations/cloud-notifications/metadata.yaml @@ -361,7 +361,7 @@ - Configuration name - you can optionally provide a name for your configuration you can easily refer to it - Rooms - by specifying a list of Rooms you are select to which nodes or areas of your infrastructure you want to be notified using this configuration - Notification - you specify which notifications you want to be notified using this configuration: All Alerts and unreachable, All Alerts, Critical only - * **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Telegram: + - **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Telegram: - Bot Token - the token of your bot - Chat ID - the chat id where your bot will deliver messages to -- cgit v1.2.3