elastic · shainaraskas · Dec 29, 2025 · Dec 29, 2025 · Dec 29, 2025 · Dec 29, 2025
@@ -4,11 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/hotspotting.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---

@@ -4,16 +4,11 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-error-handling.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---
 
-% TODO restructure ILM and SLM dtopics
+% TODO restructure ILM and SLM topics
 % TODO dropdowns or break it up
 
 # Fix index lifecycle management errors [index-lifecycle-error-handling]

@@ -3,11 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-explosion.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
+  serverless:
 products:
   - id: elasticsearch
 ---

@@ -3,11 +3,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/rejected-requests.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---

@@ -4,11 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-trb-settings.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---

@@ -1,11 +1,6 @@
 ---
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 navigation_title: "Error: Token invalid or expired"
 ---
 

@@ -3,11 +3,7 @@ navigation_title: Kibana internal server error
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-internalserver.html
 applies_to:
-  stack:
   deployment:
-    eck:
-    ess:
-    ece:
     self:
 products:
   - id: elasticsearch

@@ -4,11 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-kerberos.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---

@@ -4,11 +4,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-maccurl.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---

@@ -3,11 +3,7 @@ navigation_title: Configuration file locations
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-path.html
 applies_to:
-  stack:
   deployment:
-    eck:
-    ess:
-    ece:
     self:
 products:
   - id: elasticsearch

@@ -4,11 +4,6 @@
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-saml.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---
@@ -17,6 +12,12 @@
 
 Some of the common SAML problems are shown below with tips on how to resolve these issues.
 
+:::{note}
+This topic describes troubleshooting SAML SSO at the deployment or cluster level, for the purposes of authenticating with a {{kib}} instance. To learn about SAML SSO, for your organization or orchestrator, refer to the following topics:
+* [Elastic Cloud SAML SSO](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md)
+* [{{ece}} SAML](/deploy-manage/users-roles/cloud-enterprise-orchestrator/saml.md) and [SSO](/deploy-manage/users-roles/cloud-enterprise-orchestrator/configure-sso-for-deployments.md)
+:::
+
 1. **Symptoms:**
 
     Authentication in {{kib}} fails and the following error is printed in the {{es}} logs:

@@ -3,11 +3,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trb-security-setup.html
 applies_to:
-  stack:
   deployment:
-    eck:
-    ess:
-    ece:
     self:
 products:
   - id: elasticsearch
@@ -17,6 +13,10 @@
 
 The [elasticsearch-setup-passwords command](elasticsearch://reference/elasticsearch/command-line-tools/setup-passwords.md) 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.
 
+:::{admonition} Deprecated in 8.0
+The `elasticsearch-setup-passwords` tool is deprecated and will be removed in a future release. To manually reset the password for the built-in users (including the elastic user), use the [`elasticsearch-reset-password`](elasticsearch://reference/elasticsearch/command-line-tools/reset-password.md) tool, the {{es}} [change password API]({{es-apis}}/operation/operation-security-change-password), or the [user management features](/deploy-manage/users-roles/cluster-or-deployment-auth/native.md#managing-native-users) in {{kib}}.
+:::
+
 **Symptoms:**
 
 1. {{es}} is running HTTPS, but the command fails to detect it and returns the following errors:

@@ -1,19 +1,17 @@
 ---
-navigation_title: Active Directory
+navigation_title: Active Directory account lockout
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/trouble-shoot-active-directory.html
 applies_to:
-  stack:
   deployment:
     eck:
-    ess:
     ece:
     self:
 products:
   - id: elasticsearch
 ---
 
-# Troubleshoot Active Directory lockouts [trouble-shoot-active-directory]
+# Troubleshoot Active Directory account lockout [trouble-shoot-active-directory]
 
 **Symptoms:**
 

@@ -13,25 +13,7 @@ products:
 
 If the automatic [{{slm}}](/deploy-manage/tools/snapshot-and-restore/create-snapshots.md#automate-snapshots-slm) ({{slm-init}}) or [{{ilm}}](/manage-data/lifecycle/index-lifecycle-management.md) ({{ilm-init}}) service is not operating as expected, you might need to check its lifecycle status, stop, or restart the service. You may also want to halt services during routine maintenance.
 
-All of the procedures on this page use the {{es}} APIs. To run these steps using {{kib}}:
-
-1. Log in to the [{{ecloud}} console](https://cloud.elastic.co?page=docs&placement=docs-body).
-2. On the **Hosted deployments** panel, click the name of your deployment.
-
-    ::::{note}
-    If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include {{kib}}, all you need to do is [enable it first](../../deploy-manage/deploy/elastic-cloud/access-kibana.md).
-    ::::
-
-3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to **Dev Tools > Console**.
-
-    :::{image} /troubleshoot/images/elasticsearch-reference-kibana-console.png
-    :alt: {{kib}} Console
-    :screenshot:
-    :::
-
-4. Use the Dev Tools Console to run the API requests as described.
-
-
+You can perform the following procedures using either [API console](/explore-analyze/query-filter/tools/console.md), or direct [{{es}} API](elasticsearch://reference/elasticsearch/rest-apis/index.md) calls.
 
 ## Check status, stop, and restart {{slm-init}} [check-stop-start-slm]
 

@@ -3,11 +3,6 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/task-queue-backlog.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
 products:
   - id: elasticsearch
 ---
@@ -123,4 +118,4 @@ Related symptoms:
 * [High CPU usage](high-cpu-usage.md)
 * [Rejected requests](rejected-requests.md)
 * [Hot spotting](hotspotting.md)
-* [Troubeshooting overview](/troubleshoot/index.md)
+* [Troubleshooting overview](/troubleshoot/index.md)
@@ -4,13 +4,10 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-troubleshooting.html
 applies_to:
   stack:
-  deployment:
-    eck:
-    ess:
-    ece:
-    self:
+  serverless:
 products:
   - id: elasticsearch
+  - id: cloud-serverless
 ---
 
 # Troubleshoot transforms [transform-troubleshooting]
@@ -26,5 +23,5 @@ If you encounter problems with your transforms, you can gather more information
 * Lightweight audit messages are stored in `.transform-notifications-read`. Search by your `transform_id`.
 * The [get transform statistics API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-get-transform-stats) provides information about the transform status and failures.
 * If the transform exists as a task, you can use the [task management API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) to gather task information. For example: `GET _tasks?actions=data_frame/transforms*&detailed`. Typically, the task exists when the transform is in a started or failed state.
-* The {{es}} logs from the node that was running the transform might also contain useful information. You can identify the node from the notification messages. Alternatively, if the task still exists, you can get that information from the get transform statistics API. For more information, see [*Elasticsearch application logging*](../../deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md).
+* {applies_to}`serverless: unavailable` The {{es}} logs from the node that was running the transform might also contain useful information. You can identify the node from the notification messages. Alternatively, if the task still exists, you can get that information from the get transform statistics API. For more information, refer to [](/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md).