From cfb7f1cde96999ce425de0790b038153d31df465 Mon Sep 17 00:00:00 2001 From: Marci W <333176+marciw@users.noreply.github.com> Date: Mon, 24 Mar 2025 10:29:53 -0400 Subject: [PATCH 1/2] remove stale page --- .../deploy/cloud-enterprise/ece-ha.md | 8 ++++---- .../orchestrator/upgrade-cloud-enterprise.md | 6 +++--- redirects.yml | 3 +++ .../cloud-enterprise/ask-for-help.md | 19 ------------------- .../cloud-enterprise/common-issues.md | 2 +- .../rebuilding-broken-zookeeper-quorum.md | 2 +- .../troubleshooting-container-engines.md | 2 +- troubleshoot/index.md | 1 + troubleshoot/toc.yml | 1 - 9 files changed, 14 insertions(+), 30 deletions(-) delete mode 100644 troubleshoot/deployments/cloud-enterprise/ask-for-help.md diff --git a/deploy-manage/deploy/cloud-enterprise/ece-ha.md b/deploy-manage/deploy/cloud-enterprise/ece-ha.md index f3dec4dd43..08f2b67df6 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-ha.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-ha.md @@ -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). diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md index 8ae2a98569..c64854072f 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md @@ -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). diff --git a/redirects.yml b/redirects.yml index 9bbe46850d..d1d2e92dfc 100644 --- a/redirects.yml +++ b/redirects.yml @@ -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' \ No newline at end of file diff --git a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md b/troubleshoot/deployments/cloud-enterprise/ask-for-help.md deleted file mode 100644 index f87855aeb5..0000000000 --- a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-getting-help.html ---- - -# 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. - -Alternatively, or if you do not have a support contract, you can post in the [Elastic Cloud Enterprise forum](https://discuss.elastic.co/c/cloud-enterprise) to get help. - diff --git a/troubleshoot/deployments/cloud-enterprise/common-issues.md b/troubleshoot/deployments/cloud-enterprise/common-issues.md index 76b143a9b9..0234dc033a 100644 --- a/troubleshoot/deployments/cloud-enterprise/common-issues.md +++ b/troubleshoot/deployments/cloud-enterprise/common-issues.md @@ -149,5 +149,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). diff --git a/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md b/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md index 8a2e698556..ed89c730c0 100644 --- a/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md +++ b/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md @@ -7,7 +7,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). :::: diff --git a/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md b/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md index 59b54f85a2..3466bb0bcb 100644 --- a/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md +++ b/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md @@ -64,4 +64,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). diff --git a/troubleshoot/index.md b/troubleshoot/index.md index c9bc51f67a..03265efa93 100644 --- a/troubleshoot/index.md +++ b/troubleshoot/index.md @@ -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 diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml index ad802bfacf..e2ed0813e8 100644 --- a/troubleshoot/toc.yml +++ b/troubleshoot/toc.yml @@ -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 From ec6a6100143c1c89e8e51b9a4f378a3ecd7d55d2 Mon Sep 17 00:00:00 2001 From: Marci W <333176+marciw@users.noreply.github.com> Date: Mon, 24 Mar 2025 10:52:46 -0400 Subject: [PATCH 2/2] once more with feeling --- .../cloud-enterprise/ask-for-help.md | 22 ------------------- 1 file changed, 22 deletions(-) delete mode 100644 troubleshoot/deployments/cloud-enterprise/ask-for-help.md diff --git a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md b/troubleshoot/deployments/cloud-enterprise/ask-for-help.md deleted file mode 100644 index c645d174a3..0000000000 --- a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -applies_to: - deployment: - ece: all -mapped_pages: - - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-getting-help.html ---- - -# 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. - -Alternatively, or if you do not have a support contract, you can post in the [Elastic Cloud Enterprise forum](https://discuss.elastic.co/c/cloud-enterprise) to get help. -