elastic · marciw · Feb 19, 2025 · Feb 18, 2025 · Feb 18, 2025 · Feb 18, 2025
@@ -5,6 +5,12 @@ mapped_pages:
 
 # Ask for help [ece-getting-help]
 
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on moving this content to the [Troubleshooting overview](/troubleshoot/index.md). 
+:::
+
 For issues with Elastic Cloud Enterprise that you cannot fix yourself … we’re here to help!
 
 If you are an existing Elastic customer with a support contract, please create a ticket in the  [Elastic Support Portal](https://support.elastic.co) and provide an ECE [diagnostics package and log files](../../../deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md). By providing a diagnostics package, you make it easier for us to help you.

@@ -1,10 +1,17 @@
 ---
+navigation_title: "Elastic Cloud Enterprise"
 mapped_urls:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-find.html
 ---
 
-# Elastic Cloud Enterprise
+# Troubleshoot Elastic Cloud Enterprise
+
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure.
+:::
 
 ## Finding deployments [ts-ece-find]
 

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Zookeeper quorum"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-zookeeper-quorum.html
 ---

@@ -1,9 +1,10 @@
 ---
+navigation_title: "Removing containers"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-uninstall.html
 ---
 
-# Remove Elastic Cloud Enterprise [ece-uninstall]
+# Remove Elastic Cloud Enterprise containers  [ece-uninstall]
 
 You might need to remove Elastic Cloud Enterprise for one of the following reasons:
 
@@ -14,23 +15,18 @@ You remove Elastic Cloud Enterprise by removing all containers on the host:
 
 * If using Docker
 
-::::{admonition} 
+
 ```sh
 docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a
 ```
 
-::::
-
 
 * If using Podman
 
-::::{admonition} 
 ```sh
 sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a
 ```
 
-::::
-
 
 If you plan to reinstall Elastic Cloud Enterprise on the host, make sure you [delete the host](../../../deploy-manage/maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old Elastic Cloud Enterprise installation.
 

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Diagnostics"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-run-ece-diagnostics.html
 ---

@@ -1,9 +1,10 @@
 ---
+navigation_title: "Container engines"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-containers.html
 ---
 
-# Troubleshooting container engines [ece-troubleshooting-containers]
+# Troubleshoot container engines [ece-troubleshooting-containers]
 
 This article describes how to troubleshoot container engine services in Elastic Cloud Enterprise. We refer to [Docker](https://www.docker.com/) by default, as it’s the most common container engine, but these steps are also valid for [Podman](https://podman.io/). You can simply replace `docker` in the commands  with `podman` as needed.
 

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Emergency roles token"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-emergency.html
 ---

@@ -1,9 +1,10 @@
 ---
+navigation_title: "ZooKeeper sync status"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-zookeeper-sync.html
 ---
 
-# Verify ZooKeeper Sync Status [ece-zookeeper-sync]
+# Verify ZooKeeper sync status [ece-zookeeper-sync]
 
 It is recommended to check the ZooKeeper sync status before starting any maintenance on your Director nodes. This helps you prevent the following scenarios:
 

@@ -1,9 +1,12 @@
 ---
+navigation_title: "Common issues"
+applies:
+  eck: all
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-common-problems.html
 ---
 
-# Common problems [k8s-common-problems]
+# Troubleshoot common Elastic Cloud on Kubernetes issues [k8s-common-problems]
 
 
 ## Operator crashes on startup with `OOMKilled` [k8s-common-problems-operator-oom]

@@ -1,9 +1,12 @@
 ---
+navigation_title: "JVM heap dumps"
+applies:
+  eck: all
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-jvm-heap-dumps.html
 ---
 
-# JVM heap dumps [k8s-jvm-heap-dumps]
+# Troubleshoot JVM heap dumps [k8s-jvm-heap-dumps]
 
 ## Ensure sufficient storage [k8s_ensure_sufficient_storage]
 

@@ -8,6 +8,12 @@ mapped_pages:
 
 # Troubleshoot Elastic Cloud on Kubernetes [k8s-troubleshooting]
 
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure.
+:::
+
 * [*Common problems*](common-problems.md)
 * [*Troubleshooting methods*](troubleshooting-methods.md)
 * [*Run eck-diagnostics*](run-eck-diagnostics.md)

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Diagnostics"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-take-eck-dump.html
 ---

@@ -1,9 +1,12 @@
 ---
+navigation_title: "Resources and logs"
+applies:
+  eck: all
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-troubleshooting-methods.html
 ---
 
-# Troubleshooting methods [k8s-troubleshooting-methods]
+# Troubleshoot ECK resources and logs  [k8s-troubleshooting-methods]
 
 Most common issues can be identified and resolved by following these instructions:
 

@@ -1,3 +1,27 @@
-# Elastic Cloud
+---
+navigation_title: "Elastic Cloud"
+mapped_pages:
+  - https://www.elastic.co/guide/en/kibana/current/kibana-troubleshooting.html
+  - https://www.elastic.co/guide/en/cloud/current/ec-monitoring-diagnose-resolve.html
+---
 
-% What needs to be done: Write from scratch
+# Troubleshoot {{ecloud}}
+
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure.
+:::
+
+Use the topics in this section to troubleshoot {{ecloud}}:
+
+* [](/troubleshoot/deployments/elastic-cloud/sso.md)
+* [](/troubleshoot/monitoring/unavailable-nodes.md)
+* [](/troubleshoot/monitoring/unavailable-shards.md)
+* [](/troubleshoot/monitoring/performance.md)
+* [](/troubleshoot/monitoring/high-memory-pressure.md)
+* [](/troubleshoot/monitoring/high-availability.md)
+* [](/troubleshoot/monitoring/cluster-response-time.md)
+* [](/troubleshoot/monitoring/node-moves-outages.md)
+* [](/troubleshoot/monitoring/deployment-health-warnings.md)
+* [](/troubleshoot/monitoring/node-bootlooping.md)
@@ -12,3 +12,4 @@ Use the topics in this section to troubleshoot {{serverless-full}}:
 
 
 ## Additional resources
+[Troubleshooting overview](/troubleshoot/index.md)
@@ -4,4 +4,10 @@ navigation_title: Capacity
 
 # Troubleshoot Elasticsearch capacity issues
 
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on this section. Contributions welcome!
+:::
+
 % What needs to be done: Write from scratch
@@ -11,7 +11,7 @@ By default, the [parent circuit breaker](https://www.elastic.co/guide/en/elastic
 
 See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough of diagnosing circuit breaker errors.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -1,3 +1,13 @@
-# Clients
+---
+navigation_title: "Clients"
+---
+
+# Troubleshoot {{es}} clients
+
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on this section. Contributions welcome!
+:::
 
 % What needs to be done: Write from scratch
@@ -4,4 +4,19 @@ navigation_title: Clusters
 
 # Troubleshoot Elasticsearch clusters
 
-% What needs to be done: Write from scratch
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on this section. Contributions welcome!
+:::
+
+Use the topics in this section to troubleshoot {{es}} clusters:
+
+* [](/troubleshoot/elasticsearch/clusters.md)
+* [](/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md)
+* [](/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md)
+* [](/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md)
+* [](/troubleshoot/elasticsearch/diagnose-unassigned-shards.md)
+* [](/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md)
+* []()
+
@@ -4,6 +4,23 @@ navigation_title: Data
 
 # Troubleshoot Elasticsearch data issues
 
-% What needs to be done: Write from scratch
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on this section. Contributions welcome!
+:::
+
+Use the topics in this section to troubleshoot {{es}} data issues:
+
+* [](/troubleshoot/elasticsearch/allow-all-cluster-allocation.md)
+* [](/troubleshoot/elasticsearch/allow-all-index-allocation.md)
+* [](/troubleshoot/elasticsearch/add-tier.md)
+* [](/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md)
+* [](/troubleshoot/elasticsearch/increase-tier-capacity.md)
+* [](/troubleshoot/elasticsearch/increase-shard-limit.md)
+* [](/troubleshoot/elasticsearch/increase-cluster-shard-limit.md)
+* [](/troubleshoot/elasticsearch/corruption-troubleshooting.md)
+
+
 
 % see also fix-watermark-errors.md
@@ -233,7 +233,7 @@ For more guidance on fixing the most common causes for unassinged shards please
 :::::::
 See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::
@@ -15,7 +15,7 @@ You can generate diagnostic information using this tool before you contact [Elas
 
 See this [this video](https://www.youtube.com/watch?v=Bb6SaqhqYHw) for a walkthrough of capturing an {{es}} diagnostic.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::
@@ -69,8 +69,7 @@ To capture an {{es}} diagnostic:
     sudo .\diagnostics.bat --type local --host localhost --port 9200 -u elastic -p --bypassDiagVerify --ssl --noVerify
     ```
 
-    ::::{admonition} Script execution modes
-    :class: tip
+    ::::{tip}
 
     You can execute the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types):
 

@@ -1,13 +1,14 @@
 ---
+navigation_title: "Elasticsearch"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting.html
 ---
 
-# Elasticsearch [troubleshooting]
+# Troubleshoot {{es}} [troubleshooting]
 
 This section provides a series of troubleshooting solutions aimed at helping users fix problems that an {{es}} deployment might encounter.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -11,7 +11,7 @@ mapped_pages:
 
 This guide describes how to fix common errors and problems with {{es}} clusters.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -15,7 +15,7 @@ To prevent a full disk, when a node reaches this watermark, {{es}} [blocks write
 
 {{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.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -12,7 +12,7 @@ If a thread pool is depleted, {{es}} will [reject requests](rejected-requests.md
 
 You might experience high CPU usage if a [data tier](../../manage-data/lifecycle/data-tiers.md), and therefore the nodes assigned to that tier, is experiencing more traffic than other tiers. This imbalance in resource utilization is also known as [hot spotting](hotspotting.md).
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -7,7 +7,7 @@ mapped_pages:
 
 High JVM memory usage can degrade cluster performance and trigger [circuit breaker errors](circuit-breaker-errors.md). To prevent this, we recommend taking steps to reduce memory pressure if a node’s JVM memory usage consistently exceeds 85%.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::

@@ -11,7 +11,7 @@ mapped_pages:
 
 Computer [hot spotting](https://en.wikipedia.org/wiki/Hot_spot_(computer_programming)) may occur in {{es}} when resource utilizations are unevenly distributed across [nodes](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html). Temporary spikes are not usually considered problematic, but ongoing significantly unique utilization may lead to cluster bottlenecks and should be reviewed.
 
-::::{admonition}
+::::{tip}
 If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html).
 
 ::::
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,3 +12,4 @@ Use the topics in this section to troubleshoot {{serverless-full}}:


		## Additional resources
		[Troubleshooting overview](/troubleshoot/index.md)