0
0
Fork 0
mirror of https://github.com/netdata/netdata.git synced 2025-04-10 08:07:34 +00:00

Regenerate integrations.js ()

Co-authored-by: Ancairon <70198089+Ancairon@users.noreply.github.com>
This commit is contained in:
Netdata bot 2024-05-02 14:40:00 +03:00 committed by GitHub
parent ea98d9a9e7
commit 60f40b767a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
17 changed files with 58 additions and 58 deletions

View file

@ -23,8 +23,8 @@ Integrate your organization's Authorization Servers with Netdata to better manag
### Prerequisites
- Authorization Server with OIDC protocol supported
- A Netdata Cloud account
- Access to the Space as an administrator
- Space needs to be on the Business plan or higher
- Access to the Space as an **Admin**
- Space needs to be on a paid plan
### Setting up Authorization Server
Your server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).

View file

@ -23,8 +23,8 @@ Integrate your organization's Okta account with Netdata to better manage your te
### Prerequisites
- An Okta account
- A Netdata Cloud account
- Access to the Space as an administrator
- Space needs to be on the Business plan or higher
- Access to the Space as an **Admin**
- Space needs to be on a paid plan
### Setting up Okta
Steps needed to be done on Okta Admin Portal:

View file

@ -25,8 +25,8 @@ From the Cloud interface, you can manage your space's notification settings and
To add AWS SNS notification you need:
- A Netdata Cloud account
- Access to the space as an **administrator**
- Space needs to be on **Business** plan or higher
- Access to the space as an **Admin**
- The Space needs to be on a paid plan
- Have an AWS account with AWS SNS access, for more details check [how to configure this on AWS SNS](#settings-on-aws-sns)
### Steps

View file

@ -22,7 +22,7 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- Access to the Netdata Space as an **Admin**
- You need to have a Discord server able to receive webhooks integrations.
### Discord Server Configuration

View file

@ -23,8 +23,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Business** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have permissions on Mattermost to add new integrations.
- You need to have a Mattermost app on your workspace to receive the webhooks.

View file

@ -25,8 +25,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
To add Microsoft Teams notifications integration to your Netdata Cloud space you will need the following:
- A Netdata Cloud account.
- Access to the Netdata Cloud space as an **administrator**.
- The Space to be on **Business** plan or higher.
- Access to the Netdata Cloud space as an **Admin**.
- The Space to be on a paid plan.
- A [Microsoft 365 for Business Account](https://www.microsoft.com/en-us/microsoft-365/business). Note that this is a **paid** account.
### Settings on Microsoft Teams

View file

@ -30,7 +30,7 @@ Steps to login to the Netdata Mobile Application to receive alert and reachabili
2. Open the App and Choose the Sign In Option
- Sign In with Email Address: Enter the Email Address of your registered Netdata Cloud Account and Click on the Verification link received by Email on your mobile device.
- Sign In with QR Code: Scan the QR Code from your `Netdata Cloud` UI under **User Settings** --> **Notifications** --> **Mobile App Notifications** --> **Show QR Code**
3. Start receiving alert and reachability notifications for your **Space(s)** on a **Paid Business Subscription**
3. Start receiving alert and reachability notifications for your **Space(s)** on a **Paid Subscription plan**
### Netdata Configuration Steps
1. Click on the **User settings** on the bottom left of your screen (your profile icon)

View file

@ -23,8 +23,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Business** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have permissions on Opsgenie to add new integrations.
### Opsgenie Server Configuration

View file

@ -22,8 +22,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Business** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have a PagerDuty service to receive events using webhooks.

View file

@ -23,8 +23,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Business** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have permissions on Mattermost to add new integrations.
- You need to have a RocketChat app on your workspace to receive the webhooks.

View file

@ -23,8 +23,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Business** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have a Slack app on your workspace to receive the Webhooks.
### Slack Server Configuration

View file

@ -25,8 +25,8 @@ From the Cloud interface, you can manage your space's notification settings and
To add Splunk notification you need:
- A Netdata Cloud account
- Access to the space as an **administrator**
- Space needs to be on **Business** plan or higher
- Access to the space as an **Admin**
- The Space needs to be on a paid plan
- URI and token for your Splunk HTTP Event Collector. Refer to the [Splunk documentation](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) for detailed instructions.
### Steps

View file

@ -25,8 +25,8 @@ From the Cloud interface, you can manage your space's notification settings and
To add Splunk VictorOps notification (also known as Splunk On-Call) you need:
- A Netdata Cloud account
- Access to the space as an **administrator**
- Space needs to be on **Business** plan or higher
- Access to the space as an **Admin**
- The Space needs to be on a paid plan
- Destination URL for your Splunk VictorOps REST Endpoint Integration. Refer to the [VictorOps documentation](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide) for detailed instructions.
### Steps

View file

@ -25,8 +25,8 @@ From the Cloud interface, you can manage your space's notification settings and
To add Telegram notification you need:
- A Netdata Cloud account
- Access to the space as an **administrator**
- Space needs to be on **Business** plan or higher
- Access to the space as an **Admin**
- The Space needs to be on a paid plan
- The Telegram bot token and chat ID
### Steps

View file

@ -23,8 +23,8 @@ From the Netdata Cloud UI, you can manage your space's notification settings and
### Prerequisites
- A Netdata Cloud account
- Access to the Netdata Space as an **administrator**
- The Netdata Space needs to be on **Pro** plan or higher
- Access to the Netdata Space as an **Admin**
- The Netdata Space needs to be on a paid plan
- You need to have an app that allows you to receive webhooks following a predefined schema.
### Netdata Configuration Steps

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long