@cryptotaxi247 / netdata-1 / commits / 4952aef8e

adds docs for cloud MS Teams integration (#16834)

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>

Konstantinos Papazacharopoulos committed Jan 24, 2024 at 19:07 UTC 4952aef8ef0c7e1f9d565ed87b569f9547b2f391
1 file changed +50
integrations/cloud-notifications/metadata.yaml
+50
@@ -360,6 +360,56 @@
360 - Finally, click on **Create topic** on the bottom of the page
361 3. Now, use the new **Topic ARN** while adding AWS SNS integration on your space.
362
363 +- id: 'notify-cloud-microsoftteams'
364 + meta:
365 + name: 'Microsoft Teams'
366 + link: 'https://www.microsoft.com/en-us/microsoft-teams'
367 + categories:
368 + - notify.cloud
369 + icon_filename: 'teams.svg'
370 + keywords:
371 + - microsoft
372 + - teams
373 + overview:
374 + notification_description: "From the Netdata Cloud UI, you can manage your space's notification settings and enable the configuration to deliver notifications to a Microsoft Teams channel."
375 + notification_limitations: ''
376 + setup:
377 + description: |
378 + ### Prerequisites
379 +
380 + To add Microsoft Teams notifications integration to your Netdata Cloud space you will need the following:
381 +
382 + - A Netdata Cloud account.
383 + - Access to the Netdata Cloud space as an **administrator**.
384 + - The Space to be on **Business** plan or higher.
385 + - A [Microsoft 365 for Business Account](https://www.microsoft.com/en-us/microsoft-365/business). Note that this is a **paid** account.
386 +
387 + ### Settings on Microsoft Teams
388 +
389 + - The integration gets enabled at a team's channel level.
390 + - Click on the `...` (aka three dots) icon showing up next to the channel name, it should appear when you hover over it.
391 + - Click on `Connectors`.
392 + - Look for the `Incoming Webhook` connector and click configure.
393 + - Provide a name for your Incoming Webhook Connector, for example _Netdata Alerts_. You can also customize it with a proper icon instead of using the default image.
394 + - Click `Create`.
395 + - The _Incoming Webhook URL_ is created.
396 + - That is the URL to be provided to the Netdata Cloud configuration.
397 +
398 + ### Settings on Netdata Cloud
399 +
400 + 1. Click on the **Space settings** cog (located above your profile icon).
401 + 2. Click on the **Notification** tab.
402 + 3. Click on the **+ Add configuration** button (near the top-right corner of your screen).
403 + 4. On the **Microsoft Teams** card click on **+ Add**.
404 + 5. A modal will be presented to you to enter the required details to enable the configuration:
405 + * **Notification settings** are Netdata specific settings:
406 + - Configuration name - you can optionally provide a name for your configuration you can easily refer to it.
407 + - 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.
408 + - Notification - you specify which notifications you want to be notified using this configuration: All Alerts and unreachable, All Alerts, Critical only.
409 + * **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Microsoft Teams:
410 + - Microsoft Teams Incoming Webhook URL - the _Incoming Webhook URL_ that was generated earlier.
411 +
412 +
413 - id: 'notify-cloud-telegram'
414 meta:
415 name: 'Telegram'