Merge branch 'main' into ts-ob

Author: natasha-moore-elastic

explore-analyze/index.md

@@ -6,6 +6,7 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/elasticsearch-explore-your-data.html
   - https://www.elastic.co/guide/en/kibana/current/introduction.html#visualize-and-analyze
   - https://www.elastic.co/guide/en/kibana/current/get-started.html
+  - https://www.elastic.co/guide/en/kibana/current/accessibility.html
 ---
 
 # Explore and analyze

raw-migrated-files/cloud/cloud-enterprise/ece-config-change-errors.md

@@ -14,7 +14,7 @@ It might be helpful to temporarily block upstream requests in order to protect s
 
 * {{ecloud}} will automatically set and remove routing blocks during  plan changes. Elastic recommends avoiding manually overriding these settings for a deployment while its plans are pending.
 * The [{{es}} API console](../../../explore-analyze/query-filter/tools/console.md) bypasses {{ecloud}} proxy routing blocks against {{es}} to enable administrative tasks while plan changes are pending. You should generally default traffic to the {{es}} endpoint. However, if you enable **Stop routing requests** across all {{es}} nodes, you need to use this UI to administer your cluster.
-* While {{es}} has **Stop routing requests** set across all nodes, other products with the deployment may become unhealthy. This is because {{es}} is a prerequisite for those other products, such as {{kib}}. In {{kib}}, this results in a [**Kibana server is not ready yet**](../../../troubleshoot/kibana/error-server-not-ready.md#not-ready) message.
+* While {{es}} has **Stop routing requests** set across all nodes, other products with the deployment may become unhealthy. This is because {{es}} is a prerequisite for those other products, such as {{kib}}. In {{kib}}, this results in a [**Kibana server is not ready yet**](/troubleshoot/kibana/error-server-not-ready.md) message.
 
 
 ## Stop routing requests [ece_stop_routing_requests] 

raw-migrated-files/cloud/cloud-enterprise/ece-deployment-no-op.md

@@ -2,7 +2,7 @@
 
 Elastic Cloud Enterprise monitors many aspects of your installation, but some issues require a human to resolve them. Use this section to learn how you can:
 
-* [Find clusters](../../../troubleshoot/deployments/cloud-enterprise/finding-deployments-finding-problems.md) that have issues.
+* [Find clusters](/troubleshoot/deployments/elastic-cloud.md) that have issues.
 * [Move affected nodes off an allocator](../../../deploy-manage/maintenance/ece/move-nodes-instances-from-allocators.md), if the allocator fails.
 * [Enable deployment logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md) to keep an eye on the performance of deployments and debug stack and solution issues.