Merge branch 'main' into h1-seo

kosabogi · web-flow · commit 17c6f7432cb3 · 2025-09-19T16:20:09.000+02:00
diff --git a/deploy-manage/deploy/cloud-enterprise/fresh-installation-of-ece-using-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/fresh-installation-of-ece-using-podman-hosts.md
@@ -76,4 +76,6 @@ This section provides guidelines and recommendations to install ECE using a Podm
 
     To add a new allocator, use `--roles "allocator"`. To add a new coordinator, director, proxy, and allocator, use `--roles "allocator,coordinator,director,proxy"`
 
-
+::::{note}
+When using Podman, removing an image with the `--force` (`-f`) option not only deletes the image reference but also removes any containers that depend on that image. This behavior differs from Docker, where forced image removal does not automatically remove running or stopped containers. Therefore, avoid using the `--force` (`-f`) option with the `docker rmi` command.
+::::
diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md b/deploy-manage/deploy/cloud-enterprise/migrate-ece-to-podman-hosts.md
@@ -521,3 +521,7 @@ Using Docker or Podman as container runtime is a configuration local to the host
     5. Remove the Docker allocator by following the [Delete Hosts](../../maintenance/ece/delete-ece-hosts.md) guidelines.
 
     As an alternative, use the [Delete Runner](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-delete-runner) API.
+
+::::{note}
+When using Podman, removing an image with the `--force` (`-f`) option not only deletes the image reference but also removes any containers that depend on that image. This behavior differs from Docker, where forced image removal does not automatically remove running or stopped containers. Therefore, avoid using the `--force` (`-f`) option with the `docker rmi` command.
+::::
diff --git a/explore-analyze/discover/show-field-statistics.md b/explore-analyze/discover/show-field-statistics.md
@@ -15,6 +15,10 @@ Explore the fields in your data with the **Field statistics** view in **Discover
 * What does the latency look like when one of the containers is down on a Sunday?
 * Is the field type and format in the data view appropriate for the data and its cardinality?
 
+:::{note}
+Field statistics aren't available when **Discover** is in {{esql}} mode.
+:::
+
 This example explores the fields in the [sample web logs data](../index.md#gs-get-data-into-kibana), or you can use your own data.
 
 1. Go to **Discover**.
@@ -46,5 +50,5 @@ This example explores the fields in the [sample web logs data](../index.md#gs-ge
    :::
 
 7. Explore additional field types to see the statistics that **Discover** provides.
-8. To create a visualization of the field data, click ![Click the magnifying glass icon to create a visualization of the data in Lens](/explore-analyze/images/kibana-visualization-icon.png "") or ![Click the Maps icon to explore the data in a map](/explore-analyze/images/kibana-map-icon.png "") in the **Actions** column.
+8. To create a Lens visualization of the field data, click ![the magnifying glass icon to create a visualization of the data in Lens](/explore-analyze/images/kibana-visualization-icon.png "") or ![the Maps icon to explore the data in a map](/explore-analyze/images/kibana-map-icon.png "") in the **Actions** column.
 
diff --git a/explore-analyze/toc.yml b/explore-analyze/toc.yml
@@ -257,7 +257,6 @@ toc:
       - file: visualize/manage-panels.md
       - file: visualize/lens.md
       - file: visualize/esorql.md
-      - file: visualize/field-statistics.md
       - file: visualize/custom-visualizations-with-vega.md
       - file: visualize/text-panels.md
       - file: visualize/image-panels.md
diff --git a/explore-analyze/visualize.md b/explore-analyze/visualize.md
@@ -19,10 +19,9 @@ $$$panels-editors$$$
 | **Content** | **Panel type** | **Description** |
 | --- | --- | --- |
 | Visualizations | [Lens](visualize/lens.md) | Create powerful [charts](visualize/supported-chart-types.md) in {{kib}}. This is the default editor. |
-|  | [ES&#124;QL](/explore-analyze/query-filter/languages/esql-kibana.md) | Create visualizations from ES&#124;QL queries |
+|  | [{{esql}}](/explore-analyze/query-filter/languages/esql-kibana.md) | Create visualizations from {{esql}} queries |
 |  | [Maps](visualize/maps.md) | Create beautiful displays of your geographical data |
 |  | [Alerts](visualize/alert-panels.md) | View Observability or Security alerts in your dashboard |
-|  | [Field statistics](visualize/field-statistics.md) | Add a field statistics view of your data to your dashboards |
 |  | [Custom visualizations](visualize/custom-visualizations-with-vega.md) | Use Vega to create new types of visualizations |
 |  | | |
 | Annotations and navigation | [Collapsible sections](dashboards/arrange-panels.md#collapsible-sections) | Organize your dashboard into sections that can be collapsed and save loading time |
diff --git a/explore-analyze/visualize/field-statistics.md b/explore-analyze/visualize/field-statistics.md
diff --git a/reference/data-analysis/kibana/canvas-functions.md b/reference/data-analysis/kibana/canvas-functions.md
@@ -1,11 +1,12 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/canvas-function-reference.html
+navigation_tile: Canvas function reference
 products:
   - id: kibana
 ---
 
-# Canvas function reference [canvas-function-reference]
+# Explore Canvas functions and its expression language for {{kib}} [canvas-function-reference]
 
 Behind the scenes, Canvas is driven by a powerful expression language, with dozens of functions and other capabilities, including table transforms, type casting, and sub-expressions.
 
diff --git a/reference/fleet/data-streams.md b/reference/fleet/data-streams.md
@@ -7,7 +7,7 @@ products:
 navigation_title: Data streams
 ---
 
-# Agent-created data streams [data-streams]
+# {{agent}} data streams for {{fleet}} [data-streams]
 
 {{agent}} uses data streams to store time series data across multiple indices while giving you a single named resource for requests. Data streams are well-suited for logs, metrics, traces, and other continuously generated data. They offer a host of benefits over other indexing strategies:
 
diff --git a/reference/fleet/elasticsearch-output.md b/reference/fleet/elasticsearch-output.md
@@ -7,8 +7,7 @@ products:
   - id: elastic-agent
 ---
 
-# Configure the {{es}} output [elasticsearch-output]
-
+# Configure the {{es}} output for {{agent}} [elasticsearch-output]
 
 The {{es}} output sends events directly to {{es}} by using the {{es}} HTTP API.
 
diff --git a/solutions/observability.md b/solutions/observability.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Observability
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/what-is-observability-serverless.html
   - https://www.elastic.co/guide/en/observability/current/index.html
@@ -13,7 +14,7 @@ products:
   - id: edot-collector
 ---
 
-# Observability
+# Elastic Observability overview
 
 Elastic {{observability}} accelerates problem resolution with open, flexible, and unified observability powered by advanced machine learning and analytics. Elastic ingests all operational and business telemetry and correlates for faster root cause detection.
 
diff --git a/solutions/observability/apm/installation-layout.md b/solutions/observability/apm/installation-layout.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Installation layout
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-directory-layout.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: apm
 ---
 
-# Installation layout [apm-directory-layout]
+# Installation layout for Elastic APM Server [apm-directory-layout]
 
 View the installation layout and default paths for both Fleet-managed APM Server and the APM Server binary.
 
diff --git a/solutions/observability/apm/limitations.md b/solutions/observability/apm/limitations.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Limitations
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-open-telemetry-known-limitations.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-agents-opentelemetry-limitations.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Limitations [apm-open-telemetry-known-limitations]
+# OpenTelemetry limitations in Elastic APM [apm-open-telemetry-known-limitations]
 
 ## OpenTelemetry traces [apm-open-telemetry-traces-limitations]
 
diff --git a/solutions/observability/apm/metrics-ui.md b/solutions/observability/apm/metrics-ui.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Metrics UI
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-metrics.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-metrics.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Metrics [apm-metrics]
+# Metrics UI in Elastic APM [apm-metrics]
 
 The **Metrics** overview provides APM agent-specific metrics, which lets you perform more in-depth root cause analysis investigations within the Applications UI.
 
diff --git a/solutions/observability/apm/metrics.md b/solutions/observability/apm/metrics.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Metrics
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-data-model-metrics.html
 applies_to:
@@ -9,7 +10,7 @@ products:
   - id: apm
 ---
 
-# Metrics [apm-data-model-metrics]
+# Metrics in Elastic APM [apm-data-model-metrics]
 
 :::{include} _snippets/apm-server-vs-mis.md
 :::
diff --git a/solutions/observability/apm/traces-ui.md b/solutions/observability/apm/traces-ui.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Traces UI
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-traces.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-traces.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Traces [apm-traces]
+# Traces UI in Elastic APM [apm-traces]
 
 ::::{tip}
 Traces link together related transactions to show an end-to-end performance of how a request was served and which services were part of it. In addition to the Traces overview, you can view your application traces in the [trace sample timeline waterfall](/solutions/observability/apm/trace-sample-timeline.md).
diff --git a/solutions/observability/apm/traces.md b/solutions/observability/apm/traces.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Traces
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-distributed-tracing.html
   - https://www.elastic.co/guide/en/observability/current/apm-data-model-traces.html
@@ -10,7 +11,7 @@ products:
   - id: observability
 ---
 
-# Traces [apm-data-model-traces]
+# Traces in Elastic APM [apm-data-model-traces]
 
 A trace is a group of [transactions](/solutions/observability/apm/transactions.md) and [spans](/solutions/observability/apm/spans.md) with a common root. Each trace tracks the entirety of a single request. It describes the individual operations and their causality that ensue from a single logical operation.
 
diff --git a/solutions/observability/apm/transactions-ui.md b/solutions/observability/apm/transactions-ui.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Transactions UI
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-transactions.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-transactions.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Transactions [apm-transactions]
+# Transactions UI in Elastic APM [apm-transactions]
 
 A *transaction* describes an event captured by an Elastic APM agent instrumenting a service. APM agents automatically collect performance metrics on HTTP requests, database queries, and much more.
 
diff --git a/solutions/observability/apm/transactions.md b/solutions/observability/apm/transactions.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Transactions
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-data-model-transactions.html
 applies_to:
@@ -9,7 +10,7 @@ products:
   - id: apm
 ---
 
-# Transactions [apm-data-model-transactions]
+# Transactions in Elastic APM [apm-data-model-transactions]
 
 **Transactions** are a special kind of [span](/solutions/observability/apm/spans.md) that have additional attributes associated with them. They describe an event captured by an Elastic {{apm-agent}} instrumenting a service. You can think of transactions as the highest level of work you’re measuring within a service. As an example, a transaction might be a:
 
diff --git a/solutions/observability/apm/upgrade.md b/solutions/observability/apm/upgrade.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Upgrade
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-upgrade.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: apm
 ---
 
-# Upgrade [apm-upgrade]
+# Upgrade Elastic APM [apm-upgrade]
 
 This guide gives general recommendations for upgrading Elastic APM.
 
diff --git a/solutions/observability/incident-management/view-alerts.md b/solutions/observability/incident-management/view-alerts.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: View and manage alerts
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/view-observability-alerts.html
   - https://www.elastic.co/guide/en/serverless/current/observability-view-alerts.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# View and manage alerts [observability-view-alerts]
+# View and manage alerts in Elastic Observability [observability-view-alerts]
 
 ::::{note}
 
diff --git a/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md b/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md
@@ -87,6 +87,9 @@ If you’re upgrading from a previous version with Universal Profiling enabled,
 
 
 ### Programmatic configuration [profiling-configure-data-ingestion-programmatic]
+```{applies_to}
+stack: ga 9.2
+```
 
 If you prefer to configure data ingestion programmatically, you can use a Kibana API call. This call can be made either through the "Dev Tools" console in Kibana or with any standalone HTTP client (such as `curl` or `wget`). In both cases, the API call must be executed using the `elastic` user credentials to ensure the necessary permissions.
 
@@ -95,15 +98,15 @@ A successful API call will return a `202 Accepted` response with an empty body.
 To configure data ingestion from the console, go to **Dev Tools** in the navigation menu and run the following command:
 
 ```console
-POST kbn:/internal/profiling/setup/es_resources
+POST kbn:/api/profiling/setup/es_resources
 {}
 ```
 
 To configure data ingestion programmatically using a standalone HTTP client (e.g., `curl`), run the following command:
 
 ```console
 curl -u elastic:<PASSWORD> -H "kbn-xsrf: true" -H "Content-Type: application/json" \
-    --data "{}" "https://<kibana-host>:<kibana-port>/internal/profiling/setup/es_resources"
+    --data "{}" "https://<kibana-host>:<kibana-port>/api/profiling/setup/es_resources"
 ```
 
 
diff --git a/solutions/observability/logs/streams/management/retention.md b/solutions/observability/logs/streams/management/retention.md
@@ -1,10 +1,11 @@
 ---
+navigation_title: Manage data retention
 applies_to:
   serverless: preview
   stack: preview 9.1
 ---
 
-# Manage data retention [streams-data-retention]
+# Manage data retention for log streams [streams-data-retention]
 
 Use the **Data retention** tab on the **Manage stream** page to set how long your stream retains data and to get insight into your stream's data ingestion and storage size.
 
diff --git a/solutions/observability/synthetics/manage-data-retention.md b/solutions/observability/synthetics/manage-data-retention.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Manage data retention
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/synthetics-manage-retention.html
   - https://www.elastic.co/guide/en/serverless/current/observability-synthetics-manage-retention.html
@@ -10,7 +11,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Manage data retention [synthetics-manage-retention]
+# Manage data retention for Synthetics [synthetics-manage-retention]
 
 When you set up a synthetic monitor, data from the monitor is saved in [{{es}} data streams](/manage-data/data-store/data-streams.md), an append-only structure in {{es}}.
 
diff --git a/solutions/search/rag/playground-troubleshooting.md b/solutions/search/rag/playground-troubleshooting.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Troubleshooting
 mapped_pages:
   - https://www.elastic.co/guide/en/kibana/current/playground-troubleshooting.html
 applies_to:
@@ -8,7 +9,7 @@ products:
   - id: kibana
 ---
 
-# Troubleshooting [playground-troubleshooting]
+# Troubleshooting RAG Playground [playground-troubleshooting]
 
 ::::{warning}
 This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
diff --git a/solutions/search/rag/playground.md b/solutions/search/rag/playground.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Playground
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/elasticsearch-playground.html
   - https://www.elastic.co/guide/en/kibana/current/playground.html
@@ -10,7 +11,7 @@ products:
   - id: kibana
 ---
 
-# Playground [playground]
+# Playground for RAG [playground]
 
 Use Playground to combine your Elasticsearch data with the power of large language models (LLMs) for retrieval augmented generation (RAG). The chat interface translates your natural language questions into {{es}} queries, retrieves the most relevant results from your {{es}} documents, and passes those documents to the LLM to generate tailored responses.
 
diff --git a/solutions/search/search-applications/search-application-security.md b/solutions/search/search-applications/search-application-security.md
@@ -11,7 +11,7 @@ products:
 
 
 
-# Security [search-application-security]
+# Security for search applications [search-application-security]
 
 
 When building a frontend application for search use cases, there are two main approaches to returning search results:
diff --git a/solutions/search/vector/knn.md b/solutions/search/vector/knn.md
@@ -49,7 +49,7 @@ The default type of {{es-serverless}} project is suitable for this use case unle
 Refer to [](dense-vector.md#vector-profiles).
 :::
 
-## kNN search methods: approxiamte and exact kNN [knn-methods]
+## kNN search methods: approximate and exact kNN [knn-methods]
 
 {{es}} supports two methods for kNN search:
 
@@ -1224,7 +1224,7 @@ This example will:
 * Search using approximate kNN for the top 100 candidates.
 * Rescore the top 20 candidates (`oversample * k`) per shard using the original, non quantized vectors.
 * Return the top 10 (`k`) rescored candidates.
-* Merge the rescored canddidates from all shards, and return the top 10 (`k`) results.
+* Merge the rescored candidates from all shards, and return the top 10 (`k`) results.
 
 #### Additional rescoring techniques [dense-vector-knn-search-rescoring-rescore-additional]
 
diff --git a/solutions/security/detect-and-alert/add-manage-exceptions.md b/solutions/security/detect-and-alert/add-manage-exceptions.md
diff --git a/solutions/security/investigate/open-manage-cases.md b/solutions/security/investigate/open-manage-cases.md
diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
