Merge branch 'main' into kunisen-docpr-jira-iam1778

Author: kunisen

.github/workflows/docs-build.yml

@@ -16,4 +16,4 @@ jobs:
       deployments: write
       id-token: write
       contents: read
-      pull-requests: read
+      pull-requests: write

deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md

@@ -100,30 +100,26 @@ Make sure to use a supported combination of Linux distribution and container eng
 
     * For Podman 5
 
-        * Install version `5.2.2-13.*` using dnf.
+        * Install the latest available version of Podman `5.2.2` using dnf.
 
             :::{note}
-            As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-13` since this is the latest supported version.
-
-            If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-13` with the desired version in the commands below.
-
-            The version lock is still required for previous versions, to prevent automatic in-place updates that may be affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
+            Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later build of `5.2.2`, such as `5.2.2-16` or newer. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information.
             :::
 
             ```sh
-            sudo dnf install podman-5.2.2-13.* podman-remote-5.2.2-13.*
+            sudo dnf install podman-5.2.2 podman-remote-5.2.2
             ```
-        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-13.*`.
+        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`.
 
             ```sh
             ## Install versionlock
             sudo dnf install 'dnf-command(versionlock)'
 
             ## Lock major version
-            sudo dnf versionlock add --raw 'podman-5.2.2-13.*'
-            sudo dnf versionlock add --raw 'podman-remote-5.2.2-13.*'
+            sudo dnf versionlock add --raw 'podman-5.2.2'
+            sudo dnf versionlock add --raw 'podman-remote-5.2.2'
 
-            ## Verify that podman-5.2.2-13.* and podman-remote-5.2.2-13.* appear in the output
+            ## Verify that podman-5.2.2 and podman-remote-5.2.2 appear in the output
             sudo dnf versionlock list
             ```
 

deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md

@@ -129,30 +129,27 @@ Using Docker or Podman as container runtime is a configuration local to the host
 
     * For Podman 5
 
-        * Install version `5.2.2-13.*` using dnf.
+        * Install the latest available version of Podman `5.2.2` using dnf.
 
             :::{note}
-            As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-13` since this is the latest supported version.
-
-            If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-13` with the desired version in the commands below.
-
-            The version lock is still required for previous versions, to prevent automatic in-place updates that may be affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
+            Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this bug, use a later build of `5.2.2`, such as `5.2.2-16` or newer. Refer to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for more information.
             :::
 
             ```sh
-            sudo dnf install podman-5.2.2-13.* podman-remote-5.2.2-13.*
+            sudo dnf install podman-5.2.2 podman-remote-5.2.2
             ```
-        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-13.*`.
+
+        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2`.
 
             ```sh
             ## Install versionlock
             sudo dnf install 'dnf-command(versionlock)'
 
             ## Lock major version
-            sudo dnf versionlock add --raw 'podman-5.2.2-13.*'
-            sudo dnf versionlock add --raw 'podman-remote-5.2.2-13.*'
+            sudo dnf versionlock add --raw 'podman-5.2.2'
+            sudo dnf versionlock add --raw 'podman-remote-5.2.2'
 
-            ## Verify that podman-5.2.2-13.* and podman-remote-5.2.2-13.* appear in the output
+            ## Verify that podman-5.2.2 and podman-remote-5.2.2 appear in the output
             sudo dnf versionlock list
             ```
 

deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md

@@ -5,36 +5,27 @@ applies_to:
 ---
 # Migrating to Podman 5
 
-Following are the supported upgrade paths for Podman 5 in {{ece}}.
+This guide describes the supported ways to upgrade or migrate your {{ece}} (ECE) hosts to Podman 5. There are two primary methods:
 
-| **From ↓** ...       **To →**           | Podman 5.2.2-9 | Podman 5.2.2-11 | Podman 5.2.2-13 | Podman 5.2.3 |
-|-----------------------------------------|----------------|-----------------|-----------------|--------------|
-| **<vanilla Linux installation> (grow)** | ✓ ^*^          | ✓ ^*^           | ✓               | X            |
-| **Docker (grow-and-shrink)**            | ✓ ^*^          | ✓ ^*^           | ✓               | X            |
-| **Podman 4.9.4 (grow-and-shrink)**      | ✓ ^*^          | ✓ ^*^           | ✓               | X            |
-| **Podman 4.9.4 (in-place)**             | ✓              | X               | X               | X            |
-| **Podman 5.2.2-9 (in-place)**           | -              | X               | X               | X            |
+* **In-place upgrade**: Update Podman directly on existing ECE hosts without replacing them. In-place upgrades to Podman 5 are only supported from existing Podman-based hosts.
 
+* **Grow-and-shrink upgrade**: [Add new hosts](./install-ece-on-additional-hosts.md) running the desired Podman version to your ECE installation, then [remove the old ones](/deploy-manage/uninstall/uninstall-elastic-cloud-enterprise.md). This method is safer and preferred, as it avoids potential risks associated with upgrading the container engine or the operating system in place.
 
+ECE only supports Podman 5 in version `5.2.2`, regardless of your upgrade method. Later versions such as `5.2.3` and above are not supported. Refer always to the official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise) for details on supported versions.
 
+:::{important}
+Podman versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473). To avoid this issue, use a later build such as `5.2.2-16` or newer. 
+:::
 
-^*^ *Supported but not recommended given that a newer version (Podman `5.2.2-13`) is available.*
+The following table summarizes the supported upgrade paths to Podman 5 in ECE.
 
-Podman `5.2.2-13` is only supported when conducting a **fresh {{ece}} installation** or performing a **grow-and-shrink update** from Docker or Podman 4.
+| **From ↓** ...       **To →**           | Podman 5.2.2-latest | Podman 5.2.3 |
+|-----------------------------------------|-----------------|--------------|
+| **<vanilla Linux installation> (grow)** | ✓               | X            |
+| **Docker (grow-and-shrink)**            | ✓               | X            |
+| **Podman 4.9.4 (grow-and-shrink)**      | ✓               | X            |
+| **Podman 4.9.4 (in-place)**             | ✓               | X            |
+| **Podman 5.2.2 (grow-and-shrink)**      | ✓               | X            |
+| **Podman 5.2.2 (in-place)**             | ✓               | X            |
 
-For **in-place updates**, it is recommended to use Podman `5.2.2-9`, since upgrades to versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
-When performing an in-place update, make sure to configure the Podman version to be locked at version `5.2.2-9.*`, by following the instructions below.
-
-```sh
-## Install versionlock
-sudo dnf install 'dnf-command(versionlock)'
-
-## Lock major version
-sudo dnf versionlock add --raw 'podman-5.2.2-9.*'
-sudo dnf versionlock add --raw 'podman-remote-5.2.2-9.*'
-
-## Verify that podman-5.2.2-9.* and podman-remote-5.2.2-9.* appear in the output
-sudo dnf versionlock list
-```
-
-Podman versions `5.2.3` and higher are not supported.
+As shown in the table above, [migrations from Docker](./migrate-ece-to-podman-hosts.md) are only supported using the grow-and-shrink method.

deploy-manage/deploy/elastic-cloud/create-serverless-project.md

@@ -20,6 +20,6 @@ Choose the type of project that matches your needs and we’ll help you get star
 | --- | --- |
 |  |  |
 | ![elasticsearch](../../images/64x64_Color_elasticsearch-logo-color-64px.png "elasticsearch =50%") | **Elasticsearch**<br> Build custom search applications with {{es}}.<br><br>[**View guide →**](/solutions/search/serverless-elasticsearch-get-started.md)<br> |
-| ![observability](../../images/64x64_Color_observability-logo-color-64px.png "observability =50%") | **Observability**<br> Monitor applications and systems with Elastic Observability.<br><br>[**View guide →**](/solutions/observability/get-started/create-an-observability-project.md)<br> |
+| ![observability](../../images/64x64_Color_observability-logo-color-64px.png "observability =50%") | **Observability**<br> Monitor applications and systems with Elastic Observability.<br><br>[**View guide →**](/solutions/observability/get-started.md)<br> |
 | ![security](../../images/64x64_Color_security-logo-color-64px.png "security =50%") | **Security**<br> Detect, investigate, and respond to threats with Elastic Security.<br><br>[**View guide →**](/solutions/security/get-started/create-security-project.md)<br> |
 |  |  |

deploy-manage/deploy/elastic-cloud/serverless.md

@@ -28,7 +28,7 @@ There are differences between {{es-serverless}} and {{ech}}, for a list of diffe
 Elastic provides three serverless solutions available on {{ecloud}}. Follow these guides to get started with your serverless project:
 
 * **[{{es-serverless}}](../../../solutions/search/serverless-elasticsearch-get-started.md)**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
-* **[{{obs-serverless}}](../../../solutions/observability/get-started/create-an-observability-project.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
+* **[{{obs-serverless}}](../../../solutions/observability/get-started.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
 * **[{{sec-serverless}}](../../../solutions/security/get-started/create-security-project.md)**: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities.
 
 Afterwards, you can:

explore-analyze/query-filter/languages/esql-cross-clusters.md

@@ -469,11 +469,38 @@ FROM my-index-000001,cluster*:my-index-*,cluster_three:-my-index-000001
 ```
 
 
-## Optional remote clusters [ccq-skip-unavailable-clusters]
+## Skipping problematic remote clusters [ccq-skip-unavailable-clusters]
 
+{{ccs-cap}} for {{esql}} behavior when there are problems connecting to or running query on remote clusters differs between versions.
+
+::::{tab-set}
+
+:::{tab-item} 9.1
+Remote clusters are configured with the `skip_unavailable: true` setting by default. With this setting, clusters are marked as `skipped` or `partial` rather than causing queries to fail in the following scenarios:
+
+* The remote cluster is disconnected from the querying cluster, either before or during the query execution.
+* The remote cluster does not have the requested index, or it is not accessible due to security settings.
+* An error happened while processing the query on the remote cluster.
+
+The `partial` status means the remote query either has errors or was interrupted by an explicit user action, but some data may be returned.
+
+Queries will still fail when `skip_unavailable` is set `true`, if none of the specified indices exist. For example, the
+following queries will fail:
+
+```esql
+FROM cluster_one:missing-index | LIMIT 10
+FROM cluster_one:missing-index* | LIMIT 10
+FROM cluster_one:missing-index*,cluster_two:missing-index | LIMIT 10
+```
+:::
+
+:::{tab-item} 9.0
 If a remote cluster disconnects from the querying cluster, {{ccs}} for {{esql}} will set it to `skipped`
 and continue the query with other clusters, unless the remote cluster's `skip_unavailable` setting is set to `false`,
 in which case the query will fail.
+:::
+
+::::
 
 ## Query across clusters during an upgrade [ccq-during-upgrade]
 

manage-data/ingest/ingest-reference-architectures/agent-to-es.md

@@ -35,7 +35,7 @@ Info on {{es}}:
 
 This basic architecture is a common approach for ingesting data for the [Elastic Observability](https://www.elastic.co/observability) and [Elastic Security](https://www.elastic.co/security) solutions:
 
-* [Elastic Observability tutorials](/solutions/observability/get-started.md#_get_started_with_other_features)
+* [Elastic Observability tutorials](/solutions/observability/get-started.md)
 * [Ingest data to Elastic Security](../../../solutions/security/get-started/ingest-data-to-elastic-security.md)
 
 

redirects.yml

@@ -187,7 +187,7 @@ redirects:
   'solutions/observability/apps/analyze-monitors.md': 'solutions/observability/uptime/analyze-monitors.md'
   'solutions/observability/apps/inspect-uptime-duration-anomalies.md': 'solutions/observability/uptime/inspect-duration-anomalies.md'
   'solutions/observability/apps/configure-settings.md': 'solutions/observability/uptime/configure-settings.md'
-  'solutions/observability/apps/tutorial-monitor-java-application.md': 'solutions/observability/applications/tutorial-monitor-java-application.md'
+  'solutions/observability/apps/tutorial-monitor-java-application.md': 'solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md'
   # we can't redirect to the search-ui book so this is the next best option
   'reference/search/index.md': 'reference/index.md'
 
@@ -207,6 +207,8 @@ redirects:
   'troubleshoot/elasticsearch/elasticsearch-client-net-api/logging.md': 'troubleshoot/elasticsearch/clients.md'
   'troubleshoot/elasticsearch/elasticsearch-client-net-api/net.md': 'troubleshoot/elasticsearch/clients.md'
   'troubleshoot/elasticsearch/elasticsearch-client-ruby-api/ruby.md': 'troubleshoot/elasticsearch/clients.md'
-
+  'solutions/observability/get-started/add-data-from-splunk.md': 'solutions/observability/get-started/other-tutorials/add-data-from-splunk.md'
+  'solutions/observability/get-started/create-an-observability-project.md': 'solutions/observability/get-started.md'
+  'solutions/observability/get-started/get-started-with-dashboards.md': 'solutions/observability/get-started.md'
 # Related to https://github.com/elastic/docs-content/pull/1329
   'manage-data/ingest/transform-enrich/ingest-pipelines-serverless.md': 'manage-data/ingest/transform-enrich/ingest-pipelines.md'