Merge branch 'main' into stefnestor-patch-2

Author: kilfoyle

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.
 

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

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|QL](/explore-analyze/query-filter/languages/esql-kibana.md) | Create visualizations from ES|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 |

explore-analyze/visualize/field-statistics.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"
 ```
 
 

solutions/observability/infra-and-hosts/get-started-with-universal-profiling.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]
 

solutions/search/vector/knn.md

@@ -78,6 +78,9 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
     When you create a new exception from an alert, exception conditions are auto-populated with relevant alert data. Data from custom highlighted fields is listed first. A comment that describes the auto-generated exception conditions is also added to the **Add comments** section.
     ::::
 
+    ::::{note}
+    When using ES|QL, you can append new fields with commands such as [`EVAL`](https://www.elastic.co/docs/reference/query-languages/esql/commands/eval), but you can't apply exceptions to these appended fields. Exceptions are only applied to the index source fields.
+    ::::
 
     1. **Field**: Select a field to identify the event being filtered.
 
@@ -125,9 +128,9 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
         :screenshot:
         :::
 
-4. Click **AND** or **OR** to create multiple conditions and define their relationships.
-5. Click **Add nested condition** to create conditions using nested fields. This is only required for [these nested fields](#nested-field-list). For all other fields, nested conditions should not be used.
-6. Choose to add the exception to a rule or a shared exception list.
+5. Click **AND** or **OR** to create multiple conditions and define their relationships.
+6. Click **Add nested condition** to create conditions using nested fields. This is only required for [these nested fields](#nested-field-list). For all other fields, nested conditions should not be used.
+7. Choose to add the exception to a rule or a shared exception list.
 
     ::::{note}
     If you are creating an exception from the Shared Exception Lists page, you can add the exception to multiple rules.
@@ -138,14 +141,14 @@ You can add exceptions to a rule from the rule details page, the Alerts table, t
     If a shared exception list doesn’t exist, you can [create one](create-manage-shared-exception-lists.md) from the Shared Exception Lists page.
     ::::
 
-7. (Optional) Enter a comment describing the exception.
-8. (Optional) Enter a future expiration date and time for the exception.
-9. Select one of the following alert actions:
+8. (Optional) Enter a comment describing the exception.
+9. (Optional) Enter a future expiration date and time for the exception.
+10. Select one of the following alert actions:
 
     * **Close this alert**: Closes the alert when the exception is added. This option is only available when adding exceptions from the Alerts table.
     * **Close all alerts that match this exception and were generated by this rule**: Closes all alerts that match the exception’s conditions and were generated only by the current rule.
 
-10. Click **Add rule exception**.
+11. Click **Add rule exception**.
 
 
 ## Add {{elastic-endpoint}} exceptions [endpoint-rule-exceptions]