From 0a5dff100f5f20ead2935c73e7dac20b3e79f1a5 Mon Sep 17 00:00:00 2001 From: Naarcha-AWS Date: Thu, 17 Mar 2022 12:23:28 -0500 Subject: [PATCH] Fix final typo Signed-off-by: Naarcha-AWS --- _monitoring-plugins/alerting/monitors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_monitoring-plugins/alerting/monitors.md b/_monitoring-plugins/alerting/monitors.md index d77e58e3..205be06c 100644 --- a/_monitoring-plugins/alerting/monitors.md +++ b/_monitoring-plugins/alerting/monitors.md @@ -424,7 +424,7 @@ To create a cluster metrics monitor: 3. In the Query section, pick the **Request type** from the dropdown. 4. (Optional) If you want to filter the API response to use only certain path parameters, enter those parameters under **Query parameters**. Most APIs that can be used to monitor cluster status support path parameters as described in their documentation (e.g., comma-separated lists of index names). 5. In the Triggers section, indicate what conditions trigger an alert. The trigger condition autopopulates a painless ctx variable. For example, a cluster monitor watching for Cluster Stats uses the trigger condition `ctx.results[0].indices.count <= 0`, which triggers an alert based on the number of indexes returned by the query. For more specificity, add any additional painless conditions supported by the API. To see an example of the condition response, select **Preview condition response**. -6. In the Actions sections, indicate how you want your users to be notified when a trigger condition is met. +6. In the Actions section, indicate how you want your users to be notified when a trigger condition is met. 7. Select **Create**. Your new monitor appears in the **Monitors** list. ### Supported APIs