Remove some troubleshooting content from Deploy and manage (#450)

As part of changing 3 dupes into 3 distinct pages, this PR removes some
Kibana troubleshooting content from the Deploy and manage section so it
can live in the new consolidated Troubleshoot section.


[Preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/450/deploy-manage/deploy/self-managed/access)

(Corresponding TS files [no.
1](https://github.com/elastic/docs-content/pull/452/files#diff-eb1480bc728b8d2a24e29dec4bd920b4ac0d473de5f6336048a55e50b37a0ada)
and [no.
2](https://github.com/elastic/docs-content/pull/452/files#diff-d20506a7eb9d312fdd12e1426962fb7eed47b12184e8af23b000bc1cb9acc679)
are currently in limbo, but titles are correct here!)

Author: marciw

deploy-manage/deploy/cloud-on-k8s/kibana-instance-quickstart.md

@@ -37,7 +37,7 @@ To deploy a simple [{{kib}}](https://www.elastic.co/guide/en/kibana/current/intr
     kubectl get pod --selector='kibana.k8s.elastic.co/name=quickstart'
     ```
 
-    {{kib}} will be status `available` once [`get`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/) reports `green`. If it experiences issues starting up, use [`logs`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_logs/) against the pod in order to [Troubleshoot {{kib}} start-up](https://www.elastic.co/guide/en/kibana/current/access.html#not-ready).
+    {{kib}} will be status `available` once [`get`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/) reports `green`. If it experiences issues starting up, use [`logs`](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_logs/) against the pod in order to make sure the {{kib}} server is [ready](/troubleshoot/kibana/error-server-not-ready.md).
 
 3. Access {{kib}}.
 

deploy-manage/deploy/self-managed/access.md

@@ -33,48 +33,6 @@ If you are using a self-managed deployment, access {{kib}} through the web appli
 3. Go to the home page, then click **{{kib}}**.
 4. To make the {{kib}} page your landing page, click **Make this my landing page**.
 
-
-## Check the {{kib}} status [status]
-
-The status page displays information about the server resource usage and installed plugins.
-
-To view the {{kib}} status page, use the status endpoint. For example, `localhost:5601/status`.
-
-:::{image} ../../../images/kibana-kibana-status-page-7_14_0.png
-:alt: Kibana server status page
-:class: screenshot
-:::
-
-For JSON-formatted server status details, use the `localhost:5601/api/status` API endpoint.
-
-
-## Troubleshoot {{kib}} UI error [not-ready]
-
-Troubleshoot the `Kibana Server is not Ready yet` error.
-
-1. From within a {{kib}} node, confirm the connection to {{es}}:
-
-    ```sh
-    curl -XGET elasticsearch_ip_or_hostname:9200/
-    ```
-
-2. Guarantee the health of the three {{kib}}-backing indices.  All indices must appear and display `status:green` and `status:open`:
-
-    ```sh
-    curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session?v=true
-    ```
-
-    These {{kib}}-backing indices must also not have [index settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-settings) flagging `read_only_allow_delete` or `write` [index blocks](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html).
-
-3. [Shut down all {{kib}} nodes](../../maintenance/start-stop-services/start-stop-kibana.md).
-4. Choose any {{kib}} node, then update the config to set the [debug logging](../../monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level).
-5. [Start the node](../../maintenance/start-stop-services/start-stop-kibana.md), then check the start-up debug logs for `ERROR` messages or other start-up issues.
-
-    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.
-
-
-You can find a Kibana health troubleshooting walkthrough in [this blog](https://www.elastic.co/blog/troubleshooting-kibana-health) or in [this video](https://www.youtube.com/watch?v=AlgGYcpGvOA).
-
+## Resources
+* [Troubleshoot: Check {{kib}} server status](/troubleshoot/kibana/access.md)
+* [Troubleshoot: Error: {{kib}} server is not ready yet](/troubleshoot/kibana/error-server-not-ready.md) 

troubleshoot/elasticsearch/fix-watermark-errors.md

@@ -11,7 +11,7 @@ mapped_pages:
 
 When a data node is critically low on disk space and has reached the [flood-stage disk usage watermark](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html#cluster-routing-flood-stage), the following error is logged: `Error: disk usage exceeded flood-stage watermark, index has read-only-allow-delete block`.
 
-To prevent a full disk, when a node reaches this watermark, {{es}} [blocks writes](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html#index-block-settings) to any index with a shard on the node. If the block affects related system indices, {{kib}} and other {{stack}} features may become unavailable. For example, this could induce {{kib}}'s `Kibana Server is not Ready yet` [error message](../../deploy-manage/deploy/self-managed/access.md#not-ready).
+To prevent a full disk, when a node reaches this watermark, {{es}} [blocks writes](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html#index-block-settings) to any index with a shard on the node. If the block affects related system indices, {{kib}} and other {{stack}} features may become unavailable. For example, this could induce {{kib}}'s `Kibana Server is not Ready yet` [error message](/troubleshoot/kibana/error-server-not-ready.md).
 
 {{es}} will automatically remove the write block when the affected node’s disk usage falls below the [high disk watermark](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html#cluster-routing-watermark-high). To achieve this, {{es}} attempts to rebalance some of the affected node’s shards to other nodes in the same data tier.
 

troubleshoot/elasticsearch/monitoring-troubleshooting.md

@@ -27,7 +27,7 @@ For issues that you cannot fix yourself … we’re here to help. If you are an
 In some cases, you can also retrieve this information via APIs:
 
 * For Beat instances, use the HTTP endpoint to retrieve the `uuid` property. For example, refer to [Configure an HTTP endpoint for {{filebeat}} metrics](https://www.elastic.co/guide/en/beats/filebeat/current/http-endpoint.html).
-* For {{kib}} instances, use the [status endpoint](../../deploy-manage/deploy/self-managed/access.md#status) to retrieve the `uuid` property.
+* For {{kib}} instances, use the [status endpoint](/troubleshoot/kibana/access.md) to retrieve the `uuid` property.
 * For {{ls}} nodes, use the [monitoring APIs root resource](https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html) to retrieve the `id` property.
 
 ::::{tip} 

troubleshoot/kibana/capturing-diagnostics.md

@@ -109,4 +109,4 @@ The following are common errors that you might encounter when running the diagno
 
 * `{{kib}} Server is not Ready yet`
 
-    This indicates issues with {{kib}}'s dependencies blocking full start-up. To investigate, check [Troubleshoot {{kib}} UI error](../../deploy-manage/deploy/self-managed/access.md#not-ready).
+    This indicates issues with {{kib}}'s dependencies blocking full start-up. To investigate, check [Error: {{kib}}} server is not ready yet](/troubleshoot/kibana/error-server-not-ready.md).