From 0f049bec1e4ae293f332dc8ae459fc24edb8960b Mon Sep 17 00:00:00 2001 From: lcawl Date: Tue, 18 Jan 2022 10:12:13 -0800 Subject: [PATCH] Move section from connectors to troubleshooting --- .../alerting-troubleshooting.asciidoc | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/user/alerting/alerting-troubleshooting.asciidoc b/docs/user/alerting/alerting-troubleshooting.asciidoc index 8a39008c5f1c3..8c94683e72b4c 100644 --- a/docs/user/alerting/alerting-troubleshooting.asciidoc +++ b/docs/user/alerting/alerting-troubleshooting.asciidoc @@ -190,18 +190,7 @@ When diagnosing the health state of the task, you will most likely be interested Investigating the underlying task can help you gauge whether the problem you’re seeing is rooted in the rule not running at all, whether it’s running and failing, or whether it is running, but exhibiting behavior that is different than what was expected (at which point you should focus on the rule itself, rather than the task). -In addition to the above methods, broadly used the next approaches and common issues: - -* <> -* <> -* <> - -include::troubleshooting/alerting-common-issues.asciidoc[] -include::troubleshooting/event-log-index.asciidoc[] -include::troubleshooting/testing-connectors.asciidoc[] - - -[float] +[discrete] [[alerting-kibana-disable]] === Temporarily disable @@ -215,3 +204,14 @@ the {kib} Task Manager to gain breathing room to resolve your situation by resta xpack.task_manager.max_workers: 1 xpack.task_manager.poll_interval: 1m -------------------------------------------------- + + +In addition to the above methods, broadly used the next approaches and common issues: + +* <> +* <> +* <> + +include::troubleshooting/alerting-common-issues.asciidoc[] +include::troubleshooting/event-log-index.asciidoc[] +include::troubleshooting/testing-connectors.asciidoc[]