From fe008edaed8b5ebc724c19ca6dba9a835c366c9e Mon Sep 17 00:00:00 2001 From: Stef Nestor Date: Mon, 10 Jan 2022 11:17:44 -0700 Subject: [PATCH] [DOC] Temporarily disable Kibana Rules MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🙏🏼 per https://github.com/elastic/kibana/issues/116017, adds insight on how to temporarily disable Kibana Rules for clusters which need breathing room. --- .../alerting/alerting-troubleshooting.asciidoc | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/user/alerting/alerting-troubleshooting.asciidoc b/docs/user/alerting/alerting-troubleshooting.asciidoc index 5f3c566e82d42..8a39008c5f1c3 100644 --- a/docs/user/alerting/alerting-troubleshooting.asciidoc +++ b/docs/user/alerting/alerting-troubleshooting.asciidoc @@ -199,3 +199,19 @@ In addition to the above methods, broadly used the next approaches and common is include::troubleshooting/alerting-common-issues.asciidoc[] include::troubleshooting/event-log-index.asciidoc[] include::troubleshooting/testing-connectors.asciidoc[] + + +[float] +[[alerting-kibana-disable]] +=== Temporarily disable + +A cluster may become unresponsive or sluggish if too many or expensive {kib} rules +are attempting to run. As a stop gap measure, you may consider temporarily overriding +the {kib} Task Manager to gain breathing room to resolve your situation by restarting +{kib} after updating its config to + +[source, txt] +-------------------------------------------------- +xpack.task_manager.max_workers: 1 +xpack.task_manager.poll_interval: 1m +--------------------------------------------------