elastic · marciw · Mar 24, 2025 · Mar 24, 2025 · Mar 24, 2025 · Mar 24, 2025
@@ -63,12 +63,12 @@ Refer to [](../../reference-architectures.md) for information about {{es}} archi
 
 You should configure and use [{{es}} snapshots](/deploy-manage/tools/snapshot-and-restore.md). Snapshots provide a way to backup and restore your {{es}} indices. They can be used to copy indices for testing, to recover from failures or accidental deletions, or to migrate data to other deployments. We recommend configuring an [{{ece}}-level repository](../../tools/snapshot-and-restore/cloud-enterprise.md) to apply across all deployments. See [Work with snapshots](../../tools/snapshot-and-restore.md) for more guidance.
 
-## Furthermore considerations [ece-ece-ha-5-other]
+## Further considerations [ece-ece-ha-5-other]
 
-* Make sure you have three Zookeepers - by default, on the Director host - for your ECE installation. Similar to three Elasticsearch master nodes can form a quorum, three Zookeepers can forum the quorum for high availability purposes. Backing up Zookeeper data directory is also recommended, read [this doc](../../../troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md) for more guidance.
+* Make sure you have three Zookeepers - by default, on the Director host - for your ECE installation. Similar to three Elasticsearch master nodes can form a quorum, three Zookeepers can forum the quorum for high availability purposes. Backing up the Zookeeper data directory is also recommended: refer to [](/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md) for more guidance.
 
 * Make sure that if you’re using a [private Docker registry server](ece-install-offline-with-registry.md) or are using any [custom bundles and plugins](../../../solutions/search/full-text/search-with-synonyms.md) hosted on a web server, that these are available to all ECE allocators, so that they can continue to be accessed in the event of a network partition or zone outage.
 
-* Don’t delete containers unless guided by Elastic Support or there’s public documentation explicitly describing this as required action. Otherwise, it can cause issues and you may lose access or functionality of your {{ece}} platform. See [Troubleshooting container engines](../../../troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md) for more information.
+* Don’t delete containers unless guided by Elastic Support or there’s public documentation explicitly describing this as required action. Otherwise, it can cause issues and you may lose access or functionality of your {{ece}} platform. See [](/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md) for more information.
 
-If in doubt, please [contact support for help](../../../troubleshoot/deployments/cloud-enterprise/ask-for-help.md).
+If in doubt, please [contact support for help](/troubleshoot/index.md#contact-us).
@@ -13,7 +13,7 @@ Periodically, you might need to upgrade an Elastic Cloud Enterprise installation
 Before initiating the ECE upgrade process, consult the [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) to make sure that the Operating System (OS) and Docker or Podman versions you run are compatible with the ECE version you’re about to upgrade to. We recommend that Docker, Podman, and the operating system be at the target version before starting the ECE upgrade procedure.
 
 :::{note}
-During the upgrade window, there might be a short period of time during which you run a combination of versions which is not explicitly supported. For example, if you are on ECE 3.5 with Docker version 20.10 on Ubuntu 20.04, and plan to upgrade to ECE 3.7 on the same OS, you will need to upgrade Docker to version 24.0 first. In this case, and only during your upgrade window, we support the mixed OS/Docker versions. In general, this won’t be a problem. However, should anything become a blocker for the upgrade, [reach out to support for help](/troubleshoot/deployments/cloud-enterprise/ask-for-help.md).
+During the upgrade window, there might be a short period of time during which you run a combination of versions which is not explicitly supported. For example, if you are on ECE 3.5 with Docker version 20.10 on Ubuntu 20.04, and plan to upgrade to ECE 3.7 on the same OS, you will need to upgrade Docker to version 24.0 first. In this case, and only during your upgrade window, we support the mixed OS/Docker versions. In general, this won’t be a problem. However, should anything become a blocker for the upgrade, [reach out to support for help](/troubleshoot/index.md#contact-us).
 :::
 
 ## The upgrade version matrix [ece-upgrade-version-matrix]
@@ -43,7 +43,7 @@ The upgrade process creates a `frc-upgraders-monitor` container on the host wher
 * Monitor the upgrade process to ensure that all `frc-upgraders-upgrader` containers perform their part of the upgrade as expected and report their status.
 * After all hosts have been upgraded successfully, clean up temporary artifacts created during the upgrade process, and remove the old containers.
 
-The entire process is designed to be failsafe.  Containers get upgraded sequentially and the upgrade status of each container is tracked. The upgrade process also monitors that each new container is viable and continues to run as expected. If there is an issue with any part of the upgrade, [the entire process is rolled back](../../../troubleshoot/deployments/cloud-enterprise/common-issues.md#ece-troubleshooting-upgrade).
+The entire process is designed to be failsafe.  Containers get upgraded sequentially and the upgrade status of each container is tracked. The upgrade process also monitors that each new container is viable and continues to run as expected. If there is an issue with any part of the upgrade, [the entire process is rolled back](/troubleshoot/deployments/cloud-enterprise/common-issues.md#ece-troubleshooting-upgrade).
 
 ## Recommendations [ece-upgrade-recommendations]
 
@@ -101,7 +101,7 @@ If your ECE installation is still using the default, auto-generated certificates
     }
     ```
 
-If the license version is not 4 or higher, you must request an updated license from [Elastic Support](../../../troubleshoot/deployments/cloud-enterprise/ask-for-help.md). Once you receive your new license, make sure Elastic Cloud Enterprise is upgraded to at least version 2.5.0, and then upload the new license in the Settings page under the Platform menu.
+If the license version is not 4 or higher, you must request an updated license from [Elastic Support](/troubleshoot/index.md#contact-us). Once you receive your new license, make sure Elastic Cloud Enterprise is upgraded to at least version 2.5.0, and then upload the new license in the Settings page under the Platform menu.
 
 In versions from 2.6 to 2.10 included, some or all platform certificates are generated with a 398-day expiration. Installations that ran on these versions, even temporarily, must have their certificates rotated manually before expiry. For details, check our [KB article](https://support.elastic.co/knowledge/ECE-Certificate-Rotation).
 

@@ -82,3 +82,6 @@ redirects:
   'reference/ingestion-tools/observability/apm.md': 'reference/apm/observability/apm.md'
   'reference/ingestion-tools/observability/apm-settings.md': 'reference/apm/observability/apm-settings.md'
   'reference/ingestion-tools/fleet/migrate-from-beats-to-elastic-agent.md': 'reference/fleet/migrate-from-beats-to-elastic-agent.md'
+
+## troubleshoot
+  'troubleshoot/deployments/cloud-enterprise/ask-for-help.md': 'troubleshoot/index.md'
@@ -152,5 +152,5 @@ To determine the root cause of an upgrade failure, the following logs are availa
 `HOST_STORAGE_PATH/logs/upgrader-logs/upgrader.log`
 :   Available on every host that attempted the upgrade. This log file can tell you about the specific issues that caused the upgrade to fail on a host.
 
-In rare cases, a manual rollback of the upgrade might be required. Check [Getting help](ask-for-help.md).
+In rare cases, a manual rollback of the upgrade might be required. For more help, [contact us](/troubleshoot/index.md#contact-us).
 
@@ -10,7 +10,7 @@ mapped_pages:
 # Rebuilding a broken Zookeeper quorum [ece-troubleshooting-zookeeper-quorum]
 
 ::::{warning} 
-This article covers an advanced recovery method involving directly modifying Zookeeper. This process can potentially corrupt your data. Elastic recommends only following this outline after receiving [confirmation by Elastic Support](ask-for-help.md).
+This article covers an advanced recovery method involving directly modifying Zookeeper. This process can potentially corrupt your data. Elastic recommends only following this outline after receiving [confirmation by Elastic Support](/troubleshoot/index.md#contact-us).
 ::::
 
 

@@ -67,4 +67,4 @@ It is **not** safe to restart the following without explicit steps from Elastic
 
 For unhealthy Zookeeper, instead see [verify Zookeeper sync status](verify-zookeeper-sync-status.md) and [resolving Zookeeper quorum](rebuilding-broken-zookeeper-quorum.md).
 
-For any {{ece}} system container not listed, kindly reach out to [Elastic Support](ask-for-help.md) for advisement.
+For any {{ece}} system container not listed, reach out to [Elastic Support](/troubleshoot/index.md#contact-us).
@@ -5,6 +5,7 @@ mapped_urls:
   - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/troubleshooting-and-faqs.html
   - https://www.elastic.co/guide/en/cloud/current/ec-get-help.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-get-help.html
+  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-getting-help.html
 ---
 
 # Troubleshooting

@@ -192,7 +192,6 @@ toc:
       - file: deployments/cloud-enterprise/run-ece-diagnostics-tool.md
       - file: deployments/cloud-enterprise/heap-dumps.md
       - file: deployments/cloud-enterprise/thread-dumps.md
-      - file: deployments/cloud-enterprise/ask-for-help.md
   - file: deployments/cloud-on-k8s/kubernetes.md
     children:
       - file: deployments/cloud-on-k8s/common-problems.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -67,4 +67,4 @@ It is not safe to restart the following without explicit steps from Elastic

		For unhealthy Zookeeper, instead see [verify Zookeeper sync status](verify-zookeeper-sync-status.md) and [resolving Zookeeper quorum](rebuilding-broken-zookeeper-quorum.md).

		For any {{ece}} system container not listed, kindly reach out to [Elastic Support](ask-for-help.md) for advisement.
		For any {{ece}} system container not listed, reach out to [Elastic Support](/troubleshoot/index.md#contact-us).