From 4ebe98de16b2b5185bc770174b9f111759c1c830 Mon Sep 17 00:00:00 2001 From: Nora Date: Tue, 3 Sep 2019 13:44:41 -0700 Subject: [PATCH 01/17] Create notification-rules doc --- .../cloud/monitor-alert/notification-rules.md | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 content/v2.0/cloud/monitor-alert/notification-rules.md diff --git a/content/v2.0/cloud/monitor-alert/notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules.md new file mode 100644 index 000000000..9588a8770 --- /dev/null +++ b/content/v2.0/cloud/monitor-alert/notification-rules.md @@ -0,0 +1,38 @@ +--- +title: Create notification rules +description: > + Create notification rules to receive alerts on your time series data. + +weight: 101 +v2.0/tags: [monitor, notification rules] +menu: + v2_0: + name: Create notification rules + parent: Monitor and alert +related: + - /v2.0/monitor-alert/create-notification-endpoints/ +--- + +To receive notifications about changes in your data, start by setting up a notification endpoint. After setting up your notification endpoints, create notification rules and checks . + +## Create a notification rule in the UI + +1. On the **Monitoring and Alerting** page, next to **Notification Rules**, click **Create**. +2. In the **Name** and **Description** fields, enter a name and description for the endpoint (description used on History page? anywhere else?). +3. From the **Destination** drop-down list, select a destination to send notifications: + - (Free plan) HTTP server + - (Pay as You Go plan) HTTP server, Slack, or PagerDuty +4. Enter the **URL** to notify, and then enter connection information: + + - For HTTP: + + a. Select the **HTTP method** to use. In most cases, select **POST**. {find use cases when to use PUT & GET} + + b. Select the **auth method** to use: **None** for no authentication. To authenticate with a username and password, select **Basic** and then enter credentials in the **Username** and **Password** fields. To authenticate with a token, select **Bearer**, and then enter the authentication token in the **Token** field. + + c. In the **Content Template** field, enter {examples for each endpoint template}. + + - For Slack, enter your Slack authentication token in the **Token** field. + - For PagerDuty, enter your PagerDuty routing key in the **Routing Key** field. + +5. Click **Create Notification Endpoint**. From 5f44999373a4083a8809f139ae8da1398b9aaadb Mon Sep 17 00:00:00 2001 From: Nora Date: Tue, 3 Sep 2019 15:25:07 -0700 Subject: [PATCH 02/17] updated steps --- .../cloud/monitor-alert/notification-rules.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules.md index 9588a8770..0369ef504 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules.md @@ -18,11 +18,21 @@ To receive notifications about changes in your data, start by setting up a notif ## Create a notification rule in the UI 1. On the **Monitoring and Alerting** page, next to **Notification Rules**, click **Create**. -2. In the **Name** and **Description** fields, enter a name and description for the endpoint (description used on History page? anywhere else?). -3. From the **Destination** drop-down list, select a destination to send notifications: +2. Complete the **About** section: + a. In the **Name** field, enter a name for the notification rule. + b. In the **Schedule Every** field, enter . + c. In the **Offset** field, enter . +3. In the **Conditions** section, build a condition using a combination of status and tag keys. + +Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) + +Select status from the drop-down list (one for is equal to or two for changes from). + + +4. From the **Destination** drop-down list, select a destination to send notifications: - (Free plan) HTTP server - (Pay as You Go plan) HTTP server, Slack, or PagerDuty -4. Enter the **URL** to notify, and then enter connection information: +5. Enter the **URL** to notify, and then enter connection information: - For HTTP: From 40077c6ec067b0ba4345bfb825de64a58c31c3c5 Mon Sep 17 00:00:00 2001 From: Nora Date: Wed, 4 Sep 2019 10:13:37 -0700 Subject: [PATCH 03/17] updated doc structure for notification rules --- .../cloud/monitor-alert/notification-rules/_index.md | 0 .../create-notification-rules.md} | 4 ++-- .../notification-rules/delete-notification-rules.md | 12 ++++++++++++ .../notification-rules/update-notfication-rules.md | 12 ++++++++++++ .../notification-rules/view-notification-rules.md | 12 ++++++++++++ 5 files changed, 38 insertions(+), 2 deletions(-) create mode 100644 content/v2.0/cloud/monitor-alert/notification-rules/_index.md rename content/v2.0/cloud/monitor-alert/{notification-rules.md => notification-rules/create-notification-rules.md} (97%) create mode 100644 content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md create mode 100644 content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md create mode 100644 content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md new file mode 100644 index 000000000..e69de29bb diff --git a/content/v2.0/cloud/monitor-alert/notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md similarity index 97% rename from content/v2.0/cloud/monitor-alert/notification-rules.md rename to content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 0369ef504..4fa322097 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -8,7 +8,7 @@ v2.0/tags: [monitor, notification rules] menu: v2_0: name: Create notification rules - parent: Monitor and alert + parent: Notification rules related: - /v2.0/monitor-alert/create-notification-endpoints/ --- @@ -26,7 +26,7 @@ To receive notifications about changes in your data, start by setting up a notif Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) -Select status from the drop-down list (one for is equal to or two for changes from). +Select status from the drop-down list (one for is equal to or two for changes from). 4. From the **Destination** drop-down list, select a destination to send notifications: diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md new file mode 100644 index 000000000..057609f41 --- /dev/null +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -0,0 +1,12 @@ +--- +title: Delete notification rules +description: > + Delete notification rules to receive alerts on your time series data. + +weight: 101 +v2.0/tags: [monitor, notification rules] +menu: + v2_0: + name: Delete notification rules + parent: Notification rules +--- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md new file mode 100644 index 000000000..90ac5bdce --- /dev/null +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -0,0 +1,12 @@ +--- +title: Update notification rules +description: > + Update notification rules to receive alerts on your time series data. + +weight: 101 +v2.0/tags: [monitor, notification rules] +menu: + v2_0: + name: Update notification rules + parent: Notification rules +--- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md new file mode 100644 index 000000000..daeb19fe5 --- /dev/null +++ b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md @@ -0,0 +1,12 @@ +--- +title: View notification rules +description: > + View notification rules to receive alerts on your time series data. + +weight: 101 +v2.0/tags: [monitor, notification rules] +menu: + v2_0: + name: View notification rules + parent: Notification rules +--- From 32df8cc162b0083f107fd193915eee701713d2c1 Mon Sep 17 00:00:00 2001 From: Nora Date: Wed, 4 Sep 2019 10:37:31 -0700 Subject: [PATCH 04/17] Update frontmatter --- .../cloud/monitor-alert/notification-rules/_index.md | 11 +++++++++++ .../notification-rules/create-notification-rules.md | 2 +- .../notification-rules/delete-notification-rules.md | 2 +- .../notification-rules/update-notfication-rules.md | 2 +- .../notification-rules/view-notification-rules.md | 2 +- 5 files changed, 15 insertions(+), 4 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md index e69de29bb..4c0585f39 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md @@ -0,0 +1,11 @@ +--- +title: Manage notification rules +description: > + Manage notification rules in InfluxDB. +weight: 101 +v2.0/tags: [monitor, notification, rules] +menu: + v2_0: + name: Manage notification rules + parent: Monitor and alert +--- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 4fa322097..7398621f2 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -8,7 +8,7 @@ v2.0/tags: [monitor, notification rules] menu: v2_0: name: Create notification rules - parent: Notification rules + parent: Manage notification rules related: - /v2.0/monitor-alert/create-notification-endpoints/ --- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md index 057609f41..b3e63eeaa 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -8,5 +8,5 @@ v2.0/tags: [monitor, notification rules] menu: v2_0: name: Delete notification rules - parent: Notification rules + parent: Manage notification rules --- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index 90ac5bdce..1bbde4224 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -8,5 +8,5 @@ v2.0/tags: [monitor, notification rules] menu: v2_0: name: Update notification rules - parent: Notification rules + parent: Manage notification rules --- diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md index daeb19fe5..c78682810 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md @@ -8,5 +8,5 @@ v2.0/tags: [monitor, notification rules] menu: v2_0: name: View notification rules - parent: Notification rules + parent: Manage notification rules --- From 3e3cf944e313447e2c9e50e0ec9af609d6dc6b39 Mon Sep 17 00:00:00 2001 From: Nora Date: Wed, 4 Sep 2019 15:00:12 -0700 Subject: [PATCH 05/17] Add steps for CRUD --- .../notification-rules/_index.md | 4 +- .../create-notification-rules.md | 43 +++++++++---------- .../delete-notification-rules.md | 7 ++- .../update-notfication-rules.md | 43 ++++++++++++++++++- .../view-notification-rules.md | 13 +++++- 5 files changed, 82 insertions(+), 28 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md index 4c0585f39..a48da3364 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md @@ -2,8 +2,8 @@ title: Manage notification rules description: > Manage notification rules in InfluxDB. -weight: 101 -v2.0/tags: [monitor, notification, rules] +weight: 20 +v2.0/tags: [manage, notification, rules] menu: v2_0: name: Manage notification rules diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 7398621f2..0159939a5 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -3,46 +3,43 @@ title: Create notification rules description: > Create notification rules to receive alerts on your time series data. -weight: 101 +weight: 201 v2.0/tags: [monitor, notification rules] menu: v2_0: name: Create notification rules parent: Manage notification rules -related: - - /v2.0/monitor-alert/create-notification-endpoints/ --- -To receive notifications about changes in your data, start by setting up a notification endpoint. After setting up your notification endpoints, create notification rules and checks . +Once you've set up checks and notification endpoints, create notification rules to alert you. For details, see and . -## Create a notification rule in the UI +## Create a new notification rule in the UI -1. On the **Monitoring and Alerting** page, next to **Notification Rules**, click **Create**. +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alert" >}} + + +2. Under **Notification Rules**, click **+Create**. 2. Complete the **About** section: a. In the **Name** field, enter a name for the notification rule. b. In the **Schedule Every** field, enter . c. In the **Offset** field, enter . 3. In the **Conditions** section, build a condition using a combination of status and tag keys. + a. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) + Select status from the drop-down list (one for is equal to or two for changes from). + b. Next to **AND When**, enter one or more tag key-value pairs to filter by. +4. In the **Message** section, select an endpoint to notify. +5. Click **Create Notification Rule**. -Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) +## Clone an existing notification rule in the UI -Select status from the drop-down list (one for is equal to or two for changes from). +1. Select the **Monitoring and Alerting** icon from the sidebar. -4. From the **Destination** drop-down list, select a destination to send notifications: - - (Free plan) HTTP server - - (Pay as You Go plan) HTTP server, Slack, or PagerDuty -5. Enter the **URL** to notify, and then enter connection information: + {{< nav-icon "alert" >}} - - For HTTP: - a. Select the **HTTP method** to use. In most cases, select **POST**. {find use cases when to use PUT & GET} - - b. Select the **auth method** to use: **None** for no authentication. To authenticate with a username and password, select **Basic** and then enter credentials in the **Username** and **Password** fields. To authenticate with a token, select **Bearer**, and then enter the authentication token in the **Token** field. - - c. In the **Content Template** field, enter {examples for each endpoint template}. - - - For Slack, enter your Slack authentication token in the **Token** field. - - For PagerDuty, enter your PagerDuty routing key in the **Routing Key** field. - -5. Click **Create Notification Endpoint**. +2. Under **Notification Rules**, hover over the rule you want to clone. +3. Click the clone icon and select **Clone**. The cloned rule appears. diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md index b3e63eeaa..129b35b23 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -3,10 +3,15 @@ title: Delete notification rules description: > Delete notification rules to receive alerts on your time series data. -weight: 101 +weight: 201 v2.0/tags: [monitor, notification rules] menu: v2_0: name: Delete notification rules parent: Manage notification rules --- + +## Delete a notification rule in the UI + +1. On the **Monitoring and Alerting** page, under **Notification Rules**, hover over an existing notification rule. +2. Click the delete icon, then click **Delete** to confirm. diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index 1bbde4224..f491b2e97 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -3,10 +3,51 @@ title: Update notification rules description: > Update notification rules to receive alerts on your time series data. -weight: 101 +weight: 201 v2.0/tags: [monitor, notification rules] menu: v2_0: name: Update notification rules parent: Manage notification rules --- + +## Add a label to notification rules + +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alert" >}} + + +2. Under **Notification Rules**, click **Add a label** next to the rule you want to add a label to. The **Add Labels** box opens. +3. To add an existing label, select the label from the list. +4. To create and add a new label: + - In the search field, enter the name of the new label. The **Create Label** box opens. + - In the **Description** field, enter an optional description for the label. + - Select a color from the for the label. + - Click **Create Label**. +5. To remove a label, hover over the label next to a rule and click the X. + + +## Disable notification rules + +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alert" >}} + + +2. Under **Notification Rules**, find the rule you want to disable. +3. Click the blue toggle to disable the notification rule. + +## Update the name or description for notification rules + +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alert" >}} + + +2. Under **Notification Rules**, hover over the name or description of a rule. +3. Click the pencil icon to edit the field. +4. Click outside of the field to save your changes. diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md index c78682810..3bd3f44fa 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md @@ -3,10 +3,21 @@ title: View notification rules description: > View notification rules to receive alerts on your time series data. -weight: 101 +weight: 201 v2.0/tags: [monitor, notification rules] menu: v2_0: name: View notification rules parent: Manage notification rules --- + +## View the history for notification Rules + +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alert" >}} + + +2. Under **Notification Rules**, hover over the rule you want to view history for and click the eye icon, then click **View History** to confirm. +3. In the table that appears, review the history of alerts sent with the notification rule. From 16aec833c49ee41f1f98eeb1b47df220db5c165e Mon Sep 17 00:00:00 2001 From: Nora Date: Wed, 4 Sep 2019 15:22:26 -0700 Subject: [PATCH 06/17] Updates to content and icons --- .../notification-rules/_index.md | 3 +++ .../create-notification-rules.md | 22 +++++++++--------- .../delete-notification-rules.md | 10 ++++++-- .../update-notfication-rules.md | 6 ++--- .../view-notification-rules.md | 23 ------------------- 5 files changed, 25 insertions(+), 39 deletions(-) delete mode 100644 content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md index a48da3364..8b01ccc8a 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md @@ -9,3 +9,6 @@ menu: name: Manage notification rules parent: Monitor and alert --- +The following articles provide information on managing your notification rules: + +{{< children >}} diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 0159939a5..c02ebaf14 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -11,27 +11,27 @@ menu: parent: Manage notification rules --- -Once you've set up checks and notification endpoints, create notification rules to alert you. For details, see and . +Once you've set up checks and notification endpoints, create notification rules to alert you. For details, see and . ## Create a new notification rule in the UI 1. Select the **Monitoring and Alerting** icon from the sidebar. - {{< nav-icon "alert" >}} + {{< nav-icon "alerts" >}} 2. Under **Notification Rules**, click **+Create**. -2. Complete the **About** section: - a. In the **Name** field, enter a name for the notification rule. - b. In the **Schedule Every** field, enter . - c. In the **Offset** field, enter . -3. In the **Conditions** section, build a condition using a combination of status and tag keys. - a. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) +3. Complete the **About** section: + 1. In the **Name** field, enter a name for the notification rule. + 2. In the **Schedule Every** field, enter . + 3. In the **Offset** field, enter . +4. In the **Conditions** section, build a condition using a combination of status and tag keys. + 1. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) Select status from the drop-down list (one for is equal to or two for changes from). - b. Next to **AND When**, enter one or more tag key-value pairs to filter by. -4. In the **Message** section, select an endpoint to notify. -5. Click **Create Notification Rule**. + 2. Next to **AND When**, enter one or more tag key-value pairs to filter by. +5. In the **Message** section, select an endpoint to notify. +6. Click **Create Notification Rule**. ## Clone an existing notification rule in the UI diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md index 129b35b23..7fdd4e281 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -13,5 +13,11 @@ menu: ## Delete a notification rule in the UI -1. On the **Monitoring and Alerting** page, under **Notification Rules**, hover over an existing notification rule. -2. Click the delete icon, then click **Delete** to confirm. +1. Select the **Monitoring and Alerting** icon from the sidebar. + + + {{< nav-icon "alerts" >}} + + +2. Under **Notification Rules**, find the rule you want to disable. +3. Click the delete icon, then click **Delete** to confirm. diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index f491b2e97..c71ccfd34 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -16,7 +16,7 @@ menu: 1. Select the **Monitoring and Alerting** icon from the sidebar. - {{< nav-icon "alert" >}} + {{< nav-icon "alerts" >}} 2. Under **Notification Rules**, click **Add a label** next to the rule you want to add a label to. The **Add Labels** box opens. @@ -34,7 +34,7 @@ menu: 1. Select the **Monitoring and Alerting** icon from the sidebar. - {{< nav-icon "alert" >}} + {{< nav-icon "alerts" >}} 2. Under **Notification Rules**, find the rule you want to disable. @@ -45,7 +45,7 @@ menu: 1. Select the **Monitoring and Alerting** icon from the sidebar. - {{< nav-icon "alert" >}} + {{< nav-icon "alerts" >}} 2. Under **Notification Rules**, hover over the name or description of a rule. diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md deleted file mode 100644 index 3bd3f44fa..000000000 --- a/content/v2.0/cloud/monitor-alert/notification-rules/view-notification-rules.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: View notification rules -description: > - View notification rules to receive alerts on your time series data. - -weight: 201 -v2.0/tags: [monitor, notification rules] -menu: - v2_0: - name: View notification rules - parent: Manage notification rules ---- - -## View the history for notification Rules - -1. Select the **Monitoring and Alerting** icon from the sidebar. - - - {{< nav-icon "alert" >}} - - -2. Under **Notification Rules**, hover over the rule you want to view history for and click the eye icon, then click **View History** to confirm. -3. In the table that appears, review the history of alerts sent with the notification rule. From b3f80a6d9eb1d89450929e62d27f61f518ac44bf Mon Sep 17 00:00:00 2001 From: Nora Date: Wed, 4 Sep 2019 15:27:14 -0700 Subject: [PATCH 07/17] Add missing definition --- .../notification-rules/create-notification-rules.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index c02ebaf14..3a8b0228e 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -24,8 +24,8 @@ Once you've set up checks and notification endpoints, create notification rules 2. Under **Notification Rules**, click **+Create**. 3. Complete the **About** section: 1. In the **Name** field, enter a name for the notification rule. - 2. In the **Schedule Every** field, enter . - 3. In the **Offset** field, enter . + 2. In the **Schedule Every** field, enter how frequently the rule should run. + 3. In the **Offset** field, enter an offset time. For example, if a task is to run on the hour, a 10m offset will delay it to 10 minutes after the hour, but all time ranges defined in the task are relative to the specified execution time. 4. In the **Conditions** section, build a condition using a combination of status and tag keys. 1. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) Select status from the drop-down list (one for is equal to or two for changes from). From f5893d35c52cf18f494bcb9afbdac79b68d71101 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:22:30 -0700 Subject: [PATCH 08/17] Update _index.md --- content/v2.0/cloud/monitor-alert/notification-rules/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md index 8b01ccc8a..8f907fa01 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/_index.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/_index.md @@ -3,7 +3,7 @@ title: Manage notification rules description: > Manage notification rules in InfluxDB. weight: 20 -v2.0/tags: [manage, notification, rules] +v2.0/tags: [notifications] menu: v2_0: name: Manage notification rules From 32c06ceb9cd01a58de6e8ef5031e2eade926e183 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:22:54 -0700 Subject: [PATCH 09/17] Update create-notification-rules.md --- .../notification-rules/create-notification-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 3a8b0228e..7760c1937 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -1,7 +1,7 @@ --- title: Create notification rules description: > - Create notification rules to receive alerts on your time series data. + Create notifications to receive alerts on your time series data. weight: 201 v2.0/tags: [monitor, notification rules] From 1614aabf252433722e3a4278da64f0b7a5370704 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:23:55 -0700 Subject: [PATCH 10/17] Update create-notification-rules.md --- .../notification-rules/create-notification-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 7760c1937..dc727d446 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -25,7 +25,7 @@ Once you've set up checks and notification endpoints, create notification rules 3. Complete the **About** section: 1. In the **Name** field, enter a name for the notification rule. 2. In the **Schedule Every** field, enter how frequently the rule should run. - 3. In the **Offset** field, enter an offset time. For example, if a task is to run on the hour, a 10m offset will delay it to 10 minutes after the hour, but all time ranges defined in the task are relative to the specified execution time. + 3. In the **Offset** field, enter an offset time. For example,if a task runs on the hour, a 10m offset delays the task to 10 minutes after the hour. Time ranges defined in the task are relative to the specified execution time. 4. In the **Conditions** section, build a condition using a combination of status and tag keys. 1. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) Select status from the drop-down list (one for is equal to or two for changes from). From ce3e917885aa372dd369846b8e61e0bfb7bdfce4 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:24:56 -0700 Subject: [PATCH 11/17] Update create-notification-rules.md --- .../notification-rules/create-notification-rules.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index dc727d446..64239f4c7 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -27,8 +27,9 @@ Once you've set up checks and notification endpoints, create notification rules 2. In the **Schedule Every** field, enter how frequently the rule should run. 3. In the **Offset** field, enter an offset time. For example,if a task runs on the hour, a 10m offset delays the task to 10 minutes after the hour. Time ranges defined in the task are relative to the specified execution time. 4. In the **Conditions** section, build a condition using a combination of status and tag keys. - 1. Next to **When status**, select a an operator from the drop-down field. (either **is equal to** or **changes from**.) - Select status from the drop-down list (one for is equal to or two for changes from). + 1. Next to **When status**, select a an operator from the drop-down field: + - **is equal to** and then select the status + - **changes from** and then select both statuses 2. Next to **AND When**, enter one or more tag key-value pairs to filter by. 5. In the **Message** section, select an endpoint to notify. 6. Click **Create Notification Rule**. From abc91821116c8b2890185706692720b6ae03dc23 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:25:27 -0700 Subject: [PATCH 12/17] Update create-notification-rules.md --- .../notification-rules/create-notification-rules.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md index 64239f4c7..025166030 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/create-notification-rules.md @@ -1,10 +1,10 @@ --- title: Create notification rules description: > - Create notifications to receive alerts on your time series data. + Create notification rules to receive alerts on your time series data. -weight: 201 -v2.0/tags: [monitor, notification rules] +weight: 20 +v2.0/tags: [notifications] menu: v2_0: name: Create notification rules From 0725bfa2bf12f89ee8efa8e66c2dfbb10aa6c42f Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:25:51 -0700 Subject: [PATCH 13/17] Update delete-notification-rules.md --- .../notification-rules/delete-notification-rules.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md index 7fdd4e281..c0340f347 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -1,7 +1,8 @@ --- title: Delete notification rules description: > - Delete notification rules to receive alerts on your time series data. + If you no longer need to receive an alert, delete the associated notification rule. + weight: 201 v2.0/tags: [monitor, notification rules] From ca73dd14d8b2316b983fed710f1e27ceef844b94 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:26:29 -0700 Subject: [PATCH 14/17] Update delete-notification-rules.md --- .../notification-rules/delete-notification-rules.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md index c0340f347..ba3d61c31 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/delete-notification-rules.md @@ -5,7 +5,7 @@ description: > weight: 201 -v2.0/tags: [monitor, notification rules] +v2.0/tags: [notifications] menu: v2_0: name: Delete notification rules @@ -20,5 +20,5 @@ menu: {{< nav-icon "alerts" >}} -2. Under **Notification Rules**, find the rule you want to disable. +2. Under **Notification Rules**, find the rule you want to delete. 3. Click the delete icon, then click **Delete** to confirm. From 684ef7534dcebec996e61cdbb5e7303fffb79fc1 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:27:22 -0700 Subject: [PATCH 15/17] Update update-notfication-rules.md --- .../notification-rules/update-notfication-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index c71ccfd34..75a91e6c2 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -1,7 +1,7 @@ --- title: Update notification rules description: > - Update notification rules to receive alerts on your time series data. + Update notification rules to update the notification message or change the schedule or conditions. weight: 201 v2.0/tags: [monitor, notification rules] From 47b24206dc2a7980bada14c0fa1842b1070b572c Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:28:42 -0700 Subject: [PATCH 16/17] Update update-notfication-rules.md --- .../notification-rules/update-notfication-rules.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index 75a91e6c2..311b7c709 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -4,7 +4,7 @@ description: > Update notification rules to update the notification message or change the schedule or conditions. weight: 201 -v2.0/tags: [monitor, notification rules] +v2.0/tags: [notifications] menu: v2_0: name: Update notification rules @@ -26,7 +26,7 @@ menu: - In the **Description** field, enter an optional description for the label. - Select a color from the for the label. - Click **Create Label**. -5. To remove a label, hover over the label next to a rule and click the X. +5. To remove a label, hover over the label under to a rule and click X. ## Disable notification rules From 0050e555853e258a156b2e70547901c4c56d0bb3 Mon Sep 17 00:00:00 2001 From: noramullen1 <42354779+noramullen1@users.noreply.github.com> Date: Thu, 5 Sep 2019 10:29:21 -0700 Subject: [PATCH 17/17] Update update-notfication-rules.md --- .../notification-rules/update-notfication-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md index 311b7c709..cc0a53d23 100644 --- a/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md +++ b/content/v2.0/cloud/monitor-alert/notification-rules/update-notfication-rules.md @@ -24,7 +24,7 @@ menu: 4. To create and add a new label: - In the search field, enter the name of the new label. The **Create Label** box opens. - In the **Description** field, enter an optional description for the label. - - Select a color from the for the label. + - Select a color for the label. - Click **Create Label**. 5. To remove a label, hover over the label under to a rule and click X.