elastic · marciw · Feb 17, 2025 · Feb 12, 2025 · Feb 13, 2025 · Feb 13, 2025
@@ -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] 

@@ -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.
 

@@ -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](https://www.elastic.co/guide/en/cloud/current/ec-api-console.html) 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.
 * Enabling **Stop routing requests** does not affect your [billing](../../../deploy-manage/cloud-organization/billing.md). If needed, you can stop charges for a deployment by [deleting the deployment](../../../deploy-manage/uninstall/delete-a-cloud-deployment.md).
 
 

@@ -6,9 +6,20 @@ mapped_urls:
 
 # Elastic Cloud Enterprise
 
-% What needs to be done: Lift-and-shift
+## Finding deployments [ts-ece-find]
 
-% Use migrated content from existing pages that map to this page:
+% TODO compare to https://github.com/elastic/docs-content/tree/main/deploy-manage/deploy/cloud-enterprise/search-filter-deployments.md
 
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-troubleshooting.md
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-find.md
+When you installed Elastic Cloud Enterprise and [logged into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md) for the first time, you were greeted by two deployments. We’ve also shown you how to [create your own first deployment](../../../deploy-manage/deploy/cloud-enterprise/create-deployment.md), but that still only makes a few deployments. What if you had hundreds of deployments to look after or maybe even a thousand? How would you find the ones that need your attention?
+
+The **Deployments** page in the Cloud UI provides several ways to find deployments that might need your attention, whether that’s deployments that have a problem or deployments that are at a specific version level or really almost anything you might want to find on a complex production system:
+
+* Check the visual health indicators of deployments
+* Search for partial or whole deployment names or IDs in the search text box
+* Add filters to the **Deployments** view to filter for specific conditions:
+
+    :::{image} ../../../images/cloud-enterprise-deployment-filter.png
+    :alt: Add a filter
+    :::
+
+    Looking for all deployments of a specific version, because you want to upgrade them? Easy. Or what about that deployments you noticed before lunch that seemed to be spending an awfully long time changing its configuration—is it done? Just add a filter to find any ongoing configuration changes.
@@ -1,9 +1,12 @@
 ---
+navigation_title: "Elastic Cloud on Kubernetes"
+applies:
+  eck: all  
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-troubleshooting.html
 ---
 
-# Kubernetes [k8s-troubleshooting]
+# Troubleshoot Elastic Cloud on Kubernetes [k8s-troubleshooting]
 
 * [*Common problems*](common-problems.md)
 * [*Troubleshooting methods*](troubleshooting-methods.md)

@@ -2,4 +2,5 @@
 
 % What needs to be done: Write from scratch
 
-% Scope notes: xrefs to Monitoring section
+% Scope notes: xrefs to Monitoring section and other sections?
+% or just remove this section until later?
@@ -1,16 +1,16 @@
 ---
-navigation_title: "Troubleshooting"
+navigation_title: "Elastic Serverless Forwarder"
 mapped_pages:
   - https://www.elastic.co/guide/en/esf/current/aws-serverless-troubleshooting.html
 ---
 
 
 
-# Elastic Serverless Forwarder [aws-serverless-troubleshooting]
+# Troubleshoot Elastic Serverless Forwarder for AWS [aws-serverless-troubleshooting]
 
 
 
-## Troubleshooting deployment errors [_troubleshooting_deployment_errors]
+## Check deployment errors [_troubleshooting_deployment_errors]
 
 You can view the status of deployment actions and get additional information on events, including why a particular event fails e.g. misconfiguration details.
 
@@ -23,20 +23,19 @@ For example, if you don’t increase the visibility timeout for an SQS queue as
 
 
 
-## Preventing unexpected costs [preventing-unexpected-costs]
+## Prevent unexpected costs [preventing-unexpected-costs]
 
 It is important to monitor the Elastic Serverless Forwarder Lambda function for timeouts to prevent unexpected costs. You can use the [AWS Lambda integration](https://docs.elastic.co/en/integrations/aws/lambda) for this. If the timeouts are constant, you should throttle the Lambda function to stop its execution before proceeding with any troubleshooting steps. In most cases, constant timeouts will cause the records and messages from the event triggers to go back to their sources and trigger the function again, which will cause further timeouts and force a loop that will incure unexpected high costs. For more information on throttling Lambda functions, refer to [AWS docs](https://docs.aws.amazon.com/lambda/latest/operatorguide/throttling.md).
 
 
-### Increase debug information [_increase_debug_information]
+## Increase debug information [_increase_debug_information]
 
 To help with debugging, you can increase the amount of logging detail by adding an environment variable as follows:
 
 1. Select the serverless forwarder **application** from **Lambda > Functions**
 2. Click **Configuration** and select **Environment Variables** and choose **Edit**
 3. Click **Add environment variable** and enter `LOG_LEVEL` as **Key*** and `DEBUG` as ***Value** and click **Save**
 
-
 ## Using the Event ID format (version 1.6.0 and above) [aws-serverless-troubleshooting-event-id-format]
 
 Version 1.6.0 introduces a new event ID format that prevents duplicate ID errors when a high volume of events is ingested to {{es}}. This new format combines a timestamp with data specific to the relevant AWS resource, extracted from the AWS Lambda event received by the forwarder.
@@ -47,7 +46,7 @@ The timestamp is used as a prefix for the ID, because identifiers that gradually
 If old events that are already published to {{es}} using a version of Elastic Serverless Forwarder before v1.6.0 are ingested again, they will be treated as new events and published to {{es}} as duplicates.
 ::::
 
-
+% TODO pull out error info to separate topic
 
 ## Error handling [_error_handling]
 

@@ -0,0 +1,29 @@
+---
+navigation_title: "Check status"
+mapped_pages:
+  - https://www.elastic.co/guide/en/serverless/current/general-serverless-status.html
+---
+
+# Check Serverless status and get updates [general-serverless-status]
+
+Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
+
+To check current and past service availability, go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
+
+
+## Subscribe to updates [general-serverless-status-subscribe-to-updates]
+
+You can be notified about changes to the service status automatically.
+
+To receive service status updates:
+
+1. Go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
+2. Select **SUBSCRIBE TO UPDATES**.
+3. You can be notified in the following ways:
+
+    * Email
+    * Slack
+    * Atom or RSS feeds
+
+
+After you subscribe, you’ll be notified whenever a service status update is posted.
@@ -1,28 +1,14 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/serverless/current/general-serverless-status.html
+navigation_title: "Serverless"
 ---
 
-# Serverless [general-serverless-status]
+# Troubleshoot {{serverless-full}}
 
-Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
+Use the topics in this section to troubleshoot {{serverless-full}}:
 
-To check current and past service availability, go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
+* [](/troubleshoot/deployments/serverless-status.md)
+* [](/troubleshoot/deployments/esf/elastic-serverless-forwarder.md)
 
 
-## Subscribe to updates [general-serverless-status-subscribe-to-updates]
 
-You can be notified about changes to the service status automatically.
-
-To receive service status updates:
-
-1. Go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
-2. Select **SUBSCRIBE TO UPDATES**.
-3. You can be notified in the following ways:
-
-    * Email
-    * Slack
-    * Atom or RSS feeds
-
-
-After you subscribe, you’ll be notified whenever a service status update is posted.
+## Additional resources
@@ -35,8 +35,8 @@ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your
 
 ## Management [troubleshooting-management]
 
-* [Start index lifecycle management](start-ilm.md)
-* [Start snapshot lifecycle management](start-slm.md)
+* [Troubleshoot index and snapshot lifecycle management](start-ilm.md)
+* [Fix index lifecycle management errors](/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md)
 
 
 ## Capacity [troubleshooting-capacity]

@@ -1,10 +1,11 @@
 ---
-navgiation_title: Index lifecycle management errors
+navigation_title: "Index lifecycle management errors"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-error-handling.html
 ---
 
-% marciw consolidate ILM topics
+% TODO restructure ILM and SLM dtopics
+% TODO dropdowns or break it up
 
 # Fix index lifecycle management errors [index-lifecycle-error-handling]
 

@@ -1,5 +1,5 @@
 ---
-navigation_title: "Users command error: extra arguments" 
+navigation_title: "Error: Extra arguments provided" 
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-trb-extraargs.html
 ---

@@ -1,9 +1,10 @@
 ---
+navigation_title: Authorization errors
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-trb-roles.html
 ---
 
-# Authorization exceptions [security-trb-roles]
+# Troubleshoot authorization errors  [security-trb-roles]
 
 **Symptoms:**
 

@@ -1,10 +1,10 @@
 ---
-navigation_title: Configuration file relocation
+navigation_title: Configuration file locations
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-path.html
 ---
 
-# Failures due to relocation of the configuration files [trb-security-path]
+# Diagnose configuration file location issues [trb-security-path]
 
 **Symptoms:**
 

@@ -1,10 +1,10 @@
 ---
-navigation_title: Password setup connection failures
+navigation_title: Password setup failures
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-setup.html
 ---
 
-# Troubleshoot connection failures with elasticsearch-setup-passwords [trb-security-setup]
+# Diagnose password setup connection failures [trb-security-setup]
 
 The [elasticsearch-setup-passwords command](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-passwords.html) sets passwords for the built-in users by sending user management API requests. If your cluster uses SSL/TLS for the HTTP (REST) interface, the command attempts to establish a connection with the HTTPS protocol. If the connection attempt fails, the command fails.