From b485aab7e71c1625cfc27e0f92c9509f42378458 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 5 May 2024 13:19:16 +0200 Subject: Adding upstream version 1.45.3+dfsg. Signed-off-by: Daniel Baumann --- health/notifications/msteams/Makefile.inc | 12 --- health/notifications/msteams/README.md | 118 ----------------------------- health/notifications/msteams/metadata.yaml | 79 ------------------- 3 files changed, 209 deletions(-) delete mode 100644 health/notifications/msteams/Makefile.inc delete mode 100644 health/notifications/msteams/README.md delete mode 100644 health/notifications/msteams/metadata.yaml (limited to 'health/notifications/msteams') diff --git a/health/notifications/msteams/Makefile.inc b/health/notifications/msteams/Makefile.inc deleted file mode 100644 index f4c6995b8..000000000 --- a/health/notifications/msteams/Makefile.inc +++ /dev/null @@ -1,12 +0,0 @@ -# SPDX-License-Identifier: GPL-3.0-or-later - -# THIS IS NOT A COMPLETE Makefile -# IT IS INCLUDED BY ITS PARENT'S Makefile.am -# IT IS REQUIRED TO REFERENCE ALL FILES RELATIVE TO THE PARENT - -# install these files -dist_noinst_DATA += \ - msteams/README.md \ - msteams/Makefile.inc \ - $(NULL) - diff --git a/health/notifications/msteams/README.md b/health/notifications/msteams/README.md deleted file mode 100644 index cfda959a4..000000000 --- a/health/notifications/msteams/README.md +++ /dev/null @@ -1,118 +0,0 @@ - - -# Microsoft Teams - - - - - -You can send Netdata alerts to Microsoft Teams using Netdata's Agent alert notification feature, which supports dozens of endpoints, user roles, and more. - - - - - -## Setup - -### Prerequisites - -#### - -- The incoming webhook URL as given by Microsoft Teams. You can use the same on all your Netdata servers (or you can have multiple if you like). -- One or more channels to post the messages to -- Access to the terminal where Netdata Agent is running - - - -### Configuration - -#### File - -The configuration file name for this integration is `health_alarm_notify.conf`. - - -You can edit the configuration file using the `edit-config` script from the -Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory). - -```bash -cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata -sudo ./edit-config health_alarm_notify.conf -``` -#### Options - -The following options can be defined for this notification - -
Config Options - -| Name | Description | Default | Required | -|:----|:-----------|:-------|:--------:| -| SEND_MSTEAMS | Set `SEND_MSTEAMS` to YES | YES | yes | -| MSTEAMS_WEBHOOK_URL | set `MSTEAMS_WEBHOOK_URL` to the incoming webhook URL as given by Microsoft Teams. | | yes | -| DEFAULT_RECIPIENT_MSTEAMS | Set `DEFAULT_RECIPIENT_MSTEAMS` to the encoded Microsoft Teams channel name you want the alert notifications to be sent to. | | yes | - -##### DEFAULT_RECIPIENT_MSTEAMS - -In Microsoft Teams the channel name is encoded in the URI after `/IncomingWebhook/`. You can define multiple channels like this: `CHANNEL1` `CHANNEL2`. - -All roles will default to this variable if left unconfigured. - -You can have different channels per role, by editing `DEFAULT_RECIPIENT_MSTEAMS` with the channel you want, in the following entries at the bottom of the same file: -```conf -role_recipients_msteams[sysadmin]="CHANNEL1" -role_recipients_msteams[domainadmin]="CHANNEL2" -role_recipients_msteams[dba]="databases CHANNEL3" -role_recipients_msteams[webmaster]="CHANNEL4" -role_recipients_msteams[proxyadmin]="CHANNEL5" -role_recipients_msteams[sitemgr]="CHANNEL6" -``` - - -
- -#### Examples - -##### Basic Configuration - - - -```yaml -#------------------------------------------------------------------------------ -# Microsoft Teams (office.com) global notification options - -SEND_MSTEAMS="YES" -MSTEAMS_WEBHOOK_URL="https://outlook.office.com/webhook/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/IncomingWebhook/CHANNEL/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" -DEFAULT_RECIPIENT_MSTEAMS="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" - -``` - - -## Troubleshooting - -### Test Notification - -You can run the following command by hand, to test alerts configuration: - -```bash -# become user netdata -sudo su -s /bin/bash netdata - -# enable debugging info on the console -export NETDATA_ALARM_NOTIFY_DEBUG=1 - -# send test alarms to sysadmin -/usr/libexec/netdata/plugins.d/alarm-notify.sh test - -# send test alarms to any role -/usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE" -``` - -Note that this will test _all_ alert mechanisms for the selected role. - - diff --git a/health/notifications/msteams/metadata.yaml b/health/notifications/msteams/metadata.yaml deleted file mode 100644 index 72de507a4..000000000 --- a/health/notifications/msteams/metadata.yaml +++ /dev/null @@ -1,79 +0,0 @@ -# yamllint disable rule:line-length ---- -- id: 'notify-teams' - meta: - name: 'Microsoft Teams' - link: 'https://www.microsoft.com/en-us/microsoft-teams/log-in' - categories: - - notify.agent - icon_filename: 'msteams.svg' - keywords: - - Microsoft - - Teams - - MS teams - overview: - notification_description: | - You can send Netdata alerts to Microsoft Teams using Netdata's Agent alert notification feature, which supports dozens of endpoints, user roles, and more. - notification_limitations: '' - setup: - prerequisites: - list: - - title: '' - description: | - - The incoming webhook URL as given by Microsoft Teams. You can use the same on all your Netdata servers (or you can have multiple if you like). - - One or more channels to post the messages to - - Access to the terminal where Netdata Agent is running - configuration: - file: - name: 'health_alarm_notify.conf' - options: - description: 'The following options can be defined for this notification' - folding: - title: 'Config Options' - enabled: true - list: - - name: 'SEND_MSTEAMS' - default_value: 'YES' - description: "Set `SEND_MSTEAMS` to YES" - required: true - - name: 'MSTEAMS_WEBHOOK_URL' - default_value: '' - description: "set `MSTEAMS_WEBHOOK_URL` to the incoming webhook URL as given by Microsoft Teams." - required: true - - name: 'DEFAULT_RECIPIENT_MSTEAMS' - default_value: '' - description: "Set `DEFAULT_RECIPIENT_MSTEAMS` to the encoded Microsoft Teams channel name you want the alert notifications to be sent to." - required: true - detailed_description: | - In Microsoft Teams the channel name is encoded in the URI after `/IncomingWebhook/`. You can define multiple channels like this: `CHANNEL1` `CHANNEL2`. - - All roles will default to this variable if left unconfigured. - - You can have different channels per role, by editing `DEFAULT_RECIPIENT_MSTEAMS` with the channel you want, in the following entries at the bottom of the same file: - ```conf - role_recipients_msteams[sysadmin]="CHANNEL1" - role_recipients_msteams[domainadmin]="CHANNEL2" - role_recipients_msteams[dba]="databases CHANNEL3" - role_recipients_msteams[webmaster]="CHANNEL4" - role_recipients_msteams[proxyadmin]="CHANNEL5" - role_recipients_msteams[sitemgr]="CHANNEL6" - ``` - examples: - folding: - enabled: true - title: '' - list: - - name: 'Basic Configuration' - folding: - enabled: false - description: '' - config: | - #------------------------------------------------------------------------------ - # Microsoft Teams (office.com) global notification options - - SEND_MSTEAMS="YES" - MSTEAMS_WEBHOOK_URL="https://outlook.office.com/webhook/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/IncomingWebhook/CHANNEL/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" - DEFAULT_RECIPIENT_MSTEAMS="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" - troubleshooting: - problems: - list: [] -- cgit v1.2.3