updated content on monitoring landing page
parent
536d220665
commit
fd2b00735a
|
@ -2,7 +2,8 @@
|
|||
title: Monitor data and send alerts
|
||||
seotitle: Monitor data and send alerts
|
||||
description: >
|
||||
Monitor your time series data and send alerts by creating checks, notification rules, and notification endpoints.
|
||||
Monitor your time series data and send alerts by creating checks, notification
|
||||
rules, and notification endpoints.
|
||||
menu:
|
||||
v2_0:
|
||||
name: Monitor and alert
|
||||
|
@ -11,17 +12,29 @@ v2.0/tags: [monitor, alert, checks, notification, endpoints]
|
|||
cloud_all: true
|
||||
---
|
||||
|
||||
Monitor your time series data and send alerts by creating checks, notification rules, and notification endpoints. To get started, do the following:
|
||||
Monitor your time series data and send alerts by creating checks, notification
|
||||
rules, and notification endpoints.
|
||||
|
||||
1. [Create checks](...create-a-check) to monitor data for a specified check status.
|
||||
2. (Optional) Send alerts on a specified check status by doing the following:
|
||||
InfluxDB lets
|
||||
|
||||
a. [Create a notification endpoint](/v2.0/monitor-alert/notification-endpoints/create).
|
||||
## The monitoring workflow
|
||||
1. InfluxDB uses a [check](/v2.0/reference/glossary/#check) to query data and
|
||||
assigns a status or `_level` based on specific conditions.
|
||||
2. InfluxDB stores the output the check in the `statuses` measurement in the `_monitoring` system bucket.
|
||||
3. [Notification rules](/v2.0/reference/glossary/#notification-rule) check data in the `statuses`
|
||||
measurement and, based conditions set in the notification rule, send a message
|
||||
to a [notification endpoint](/v2.0/reference/glossary/#notification-endpoint).
|
||||
4. InfluxDB stores notifications in the `notifications` measurement in the `_monitoring` system bucket.
|
||||
|
||||
b. [Create notification rules](/v2.0/monitor-alert/notification-rules/create).
|
||||
## Monitor your data
|
||||
To get started, do the following:
|
||||
|
||||
After creating your initial checks and notifications, adjust how you monitor data and alerts as needed. For more information, see:
|
||||
1. [Create checks](/v2.0/monitor-alert/checks/create/) to monitor data and assign a status.
|
||||
2. [Add notification endpoints](/v2.0/monitor-alert/notification-endpoints/create/) to send notifications to.
|
||||
3. [Create notification rules](/v2.0/monitor-alert/notification-rules/create) to check
|
||||
statuses and send notifications to your notifications endpoints.
|
||||
|
||||
- [Manage checks](/v2.0/cloud/monitor-alert/manage-checks)
|
||||
- [Manage notification rules](/v2.0/monitor-alert/notification-rules)
|
||||
- [Manage notification endpoints](/v2.0/monitor-alert/notification-endpoints)
|
||||
|
||||
## Manage your monitoring and alerting pipeline
|
||||
|
||||
{{< children >}}
|
||||
|
|
|
@ -14,7 +14,7 @@ related:
|
|||
cloud_all: true
|
||||
---
|
||||
|
||||
InfluxDB checks query data and apply a status or level to each data point based on specified conditions.
|
||||
Checks in InfluxDB query data and apply a status or level to each data point based on specified conditions.
|
||||
Learn how to create and manage checks:
|
||||
|
||||
{{< children >}}
|
||||
|
|
|
@ -39,9 +39,7 @@ _For details, see [Manage checks](/v2.0/monitor-alert/checks/) and
|
|||
|
||||
1. Select the **Monitoring and Alerting** icon from the sidebar.
|
||||
|
||||
|
||||
{{< nav-icon "alerts" >}}
|
||||
|
||||
|
||||
2. Under **Notification Rules**, hover over the rule you want to clone.
|
||||
3. Click the clone icon and select **Clone**. The cloned rule appears.
|
||||
|
|
Loading…
Reference in New Issue