From 0602c74618b7536167f763c173a70912d2b3c398 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Sun, 3 Mar 2024 18:51:05 -0700 Subject: [PATCH 1/2] (DOC+) Link Kibana Health Troubleshooting blog to related doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 👋 howdy, team! I would like to link our Kibana+Security+ResponseOps Dev approved blog on [Troubleshooting Kibana Health](https://www.elastic.co/blog/troubleshooting-kibana-health) to the Kibana doc section about [Troubleshooting Kibana UI error](https://www.elastic.co/guide/en/kibana/master/access.html#not-ready) (as it was intended as the more verbose / commentary version of the doc). --- docs/setup/access.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/setup/access.asciidoc b/docs/setup/access.asciidoc index 631fa22d711d..2283a1e74059 100644 --- a/docs/setup/access.asciidoc +++ b/docs/setup/access.asciidoc @@ -63,3 +63,5 @@ For example: * When {kib} is unable to connect to a healthy {es} cluster, errors like `master_not_discovered_exception` or `unable to revive connection` or `license is not available` errors appear. * When one or more {kib}-backing indices are unhealthy, the `index_not_green_timeout` error appears. + +Kindly also reference our https://www.elastic.co/blog/troubleshooting-kibana-health[walkthrough on troubleshooting Kibana Health]. From 0e00a8e3b714c5ad30f9025fb7c1d8b181b773e5 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Tue, 5 Mar 2024 10:50:32 -0700 Subject: [PATCH 2/2] feedback Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com> --- docs/setup/access.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/setup/access.asciidoc b/docs/setup/access.asciidoc index 2283a1e74059..f0bb75621c04 100644 --- a/docs/setup/access.asciidoc +++ b/docs/setup/access.asciidoc @@ -64,4 +64,4 @@ For example: * When {kib} is unable to connect to a healthy {es} cluster, errors like `master_not_discovered_exception` or `unable to revive connection` or `license is not available` errors appear. * When one or more {kib}-backing indices are unhealthy, the `index_not_green_timeout` error appears. -Kindly also reference our https://www.elastic.co/blog/troubleshooting-kibana-health[walkthrough on troubleshooting Kibana Health]. +For more information, refer to our https://www.elastic.co/blog/troubleshooting-kibana-health[walkthrough on troubleshooting Kibana Health].