(DOC+) Link Kibana Health Troubleshooting blog to related doc (#177907)

## Summary

👋 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).


### Checklist

Delete any items that are not applicable to this PR.

### Risk Matrix


### For maintainers

- [X] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
This commit is contained in:
Stef Nestor 2024-03-05 11:15:27 -07:00 committed by GitHub
parent 8f9c130a06
commit 4cc38e7025
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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.
For more information, refer to our https://www.elastic.co/blog/troubleshooting-kibana-health[walkthrough on troubleshooting Kibana Health].