diff options
| author | Juan Cañete <2930882+juacker@users.noreply.github.com> | 2023-11-17 17:44:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-17 17:44:19 +0100 |
| commit | 4e20b15cb9965436fa89acf3a3caff43a9a0c37d (patch) | |
| tree | ac95e6a0b24642569c9b3e999d3f5fa68db6fc1e | |
| parent | f7abb81f76eaaf7beda1d6bb5589f5e43570945d (diff) | |
Update integrations/cloud-notifications/metadata.yamlfeat/adds-cloud-notification-telegram-doc
Co-authored-by: Tasos Katsoulas <12612986+tkatsoulas@users.noreply.github.com>
| -rw-r--r-- | integrations/cloud-notifications/metadata.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
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 |