Merge pull request #472 from influxdata/update/alerts-oss
Removed cloud tags from alerts docspull/497/head
Scott Anderson
GitHub
commit
8696abfcfb
|
|
@ -9,7 +9,6 @@ menu:
|
|||
name: Monitor & alert
|
||||
weight: 6
|
||||
v2.0/tags: [monitor, alert, checks, notification, endpoints]
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Monitor your time series data and send alerts by creating checks, notification
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ v2.0/tags: [monitor, checks, notifications, alert]
|
|||
related:
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 201
|
|||
related:
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Create a check in the InfluxDB user interface (UI).
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 204
|
|||
related:
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
If you no longer need a check, use the InfluxDB user interface (UI) to delete it.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 203
|
|||
related:
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Update checks in the InfluxDB user interface (UI).
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 202
|
|||
related:
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
View check details and statuses and notifications generated by checks in the InfluxDB user interface (UI).
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ weight: 102
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Notification endpoints store information to connect to a third party service.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 201
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
To send notifications about changes in your data, start by creating a notification endpoint to a third party service. After creating notification endpoints, [create notification rules](/v2.0/monitor-alert/notification-rules/create) to send alerts to third party services on [check statuses](/v2.0/monitor-alert/checks/create).
|
||||
|
|
@ -26,11 +25,11 @@ To send notifications about changes in your data, start by creating a notificati
|
|||
The following endpoints are available for InfluxDB 2.0 OSS, the InfluxDB Cloud 2.0 Free Plan,
|
||||
and the InfluxDB Cloud 2.0 Pay As You Go (PAYG) Plan:
|
||||
|
||||
| Endpoint | OSS | Free Plan _(Cloud)_ | PAYG Plan _(Cloud)_ |
|
||||
|:-------- |:--------:|:-------------------: |:----------------------------:|
|
||||
| **Slack** | _Coming_ | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| **PagerDuty** | _Coming_ | | **{{< icon "check" >}}** |
|
||||
| **HTTP** | _Coming_ | | **{{< icon "check" >}}** |
|
||||
| Endpoint | OSS | Free Plan _(Cloud)_ | PAYG Plan _(Cloud)_ |
|
||||
|:-------- |:--------: |:-------------------: |:----------------------------:|
|
||||
| **Slack** | **{{< icon "check" >}}** | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| **PagerDuty** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
|
||||
| **HTTP** | **{{< icon "check" >}}** | | **{{< icon "check" >}}** |
|
||||
|
||||
4. In the **Name** and **Description** fields, enter a name and description for the endpoint.
|
||||
5. Enter enter information to connect to the endpoint:
|
||||
|
|
@ -40,7 +39,7 @@ To send notifications about changes in your data, start by creating a notificati
|
|||
- For Slack, create an [Incoming WebHook](https://api.slack.com/incoming-webhooks#posting_with_webhooks) in Slack, and then enter your webHook URL in the **Slack Incoming WebHook URL** field.
|
||||
|
||||
- For PagerDuty:
|
||||
- [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service), [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service), and then enter the PagerDuty integration key for your new service in the **Routing Key** field.
|
||||
- [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service), [add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service), and then enter the PagerDuty integration key for your new service in the **Routing Key** field.
|
||||
- The **Client URL** provides a useful link in your PagerDuty notification. Enter any URL that you'd like to use to investigate issues. This URL is sent as the `client_url` property in the PagerDuty trigger event. By default, the **Client URL** is set to your Monitoring & Alerting History page, and the following included in the PagerDuty trigger event: `"client_url": "https://twodotoh.a.influxcloud.net/orgs/<your-org-ID>/alert-history”`
|
||||
|
||||
6. Click **Create Notification Endpoint**.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 204
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
If notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then [update notification rules](/v2.0/monitor-alert/notification-rules/update) with a new notification endpoint as needed.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ weight: 203
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/).
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ weight: 202
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-rules/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
View notification endpoint details and history in the InfluxDB user interface (UI).
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ menu:
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
The following articles provide information on managing your notification rules:
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ menu:
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
Once you've set up checks and notification endpoints, create notification rules to alert you.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ menu:
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
## Delete a notification rule in the UI
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ menu:
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
## Add a label to notification rules
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ menu:
|
|||
related:
|
||||
- /v2.0/monitor-alert/checks/
|
||||
- /v2.0/monitor-alert/notification-endpoints/
|
||||
cloud_all: true
|
||||
---
|
||||
|
||||
View notification rule details and statuses and notifications generated by notification rules in the InfluxDB user interface (UI).
|
||||
|
|
|
|||
Loading…
Reference in New Issue