Merge branch 'main' into szabosteve/eis-support-page

Author: szabosteve

explore-analyze/transforms/transform-limitations.md

@@ -123,6 +123,55 @@ If your data uses the [date nanosecond data type](elasticsearch://reference/elas
 
 If you use ILM to have time-based indices, consider using the [Date index name](elasticsearch://reference/enrich-processor/date-index-name-processor.md) instead. The processor works without duplicated documents if your {{transform}} contains a `group_by` based on `date_histogram`.
 
+### SLO transforms at scale may misreport state and increase PIT activity
+
+When running a large number of SLO {{transforms}}, two types of limitations can appear:
+
+- {{transforms-cap}} may [misreport](#transforms-inaccurate-errors) their state and suggest deletion even though they are still valid
+- Point-in-time (PIT) requests may [accumulate](#transforms-pit-overloads), creating extra activity on the cluster and slowing down operations
+
+#### {{transforms-cap}} can return inaccurate errors that suggest deletion [transforms-inaccurate-errors]
+
+The {{transforms-cap}} API and the {{transforms-cap}} page in {{kib}} (**Stack Management** > **{{transforms-cap}})** may display misleading error messages for {{transforms}} created by service level objectives (SLOs).
+
+The message typically reads:
+
+```console
+Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.
+```
+Although the error suggests that the {{transform}} is broken and should be deleted, this is usually not the case. The error occurs because of a limitation in how the {{transforms}} are queried and presented by the API and UI. Deleting the {{transform}} can break related SLOs.
+
+If you encounter this error, do not delete the {{transform}}. If a {{transform}} was already deleted, you can restore it by resetting the SLO, either in the {{kib}} or with the API:
+
+- In {{kib}}, go to the **Observability** > **SLOs application**, open the menu for the affected SLO, and click **Reset**. 
+
+- If you use the API, run the following request:
+
+  ```console
+  POST kbn:/api/observability/slos/<SLO_ID>/_reset
+  ```
+
+#### Large numbers of {{transform}} can cause PIT overloads [transforms-pit-overloads]
+
+{{transforms-cap}} rely on point-in-time (PIT) searches to ensure that queries remain consistent during data changes. Each {{transform}} can open and close multiple PITs during its lifetime. 
+
+When many {{transforms}} run concurrently, especially in environments with large numbers of SLOs (hundreds to more than a thousand transforms), PITs can be opened and closed in quick succession. Because PITs are closed asynchronously, the close operation does not wait for the previous request to complete. This can create a backlog of PIT close requests, known as a PIT overload.
+
+A PIT overload increases the memory pressure on hot nodes. This may result in rising memory usage and long garbage collection cycles. In practice, searches and writes may slow down or queue until the node recovers, and in severe cases a restart may be required.
+
+As a workaround, you can disable PIT for a specific {{transform}}:
+
+```console
+POST _transform/<transform_id>/_update
+{
+  "settings": {
+    "use_point_in_time": false
+  }
+}
+```
+
+To fix this issue permanently, upgrade to the following versions or later: 8.18.8, 8.19.5, 9.0.8, 9.1.5, or 9.2.0.
+
 ## Limitations in {{kib}} [transform-ui-limitations]
 
 ### {{transforms-cap}} are visible in all {{kib}} spaces [transform-space-limitations]

manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md

@@ -150,7 +150,7 @@ To add an index template to a cluster and apply the lifecycle policy to indices
 1. On the **Component templates** page, use the search and filter tools to select any [component templates](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-component-template) to include in the index template. The index template will inherit the settings, mappings, and aliases defined in the component templates and apply them to indices when they're created.
 
 1. On the **Index settings** page:
-    1. Configure ILM by specifying the [ILM settings](https://www.elastic.co/docs/api/doc/elasticsearch/configuration-reference/index-lifecycle-management-settings#_index_level_settings_2) to apply to the indices:
+    1. Configure ILM by specifying the [ILM settings](elasticsearch://reference/elasticsearch/configuration-reference/index-lifecycle-management-settings.md) to apply to the indices:
         * `index.lifecycle.name` - The lifecycle policy to manage the created indices.
         * `index.lifecycle.rollover_alias` - The index [alias](/manage-data/data-store/aliases.md) used for querying and managing the set of indices associated with a lifecycle policy that contains a rollover action.
 

reference/fleet/example-standalone-monitor-nginx-serverless.md

@@ -315,3 +315,4 @@ Congratulations! You have successfully set up monitoring for nginx using standal
 
 * Learn more about [{{fleet}} and {{agent}}](/reference/fleet/index.md).
 * Learn more about [{{integrations}}](integration-docs://reference/index.md).
+* Learn how to manage your [data lifecycle](/manage-data/lifecycle.md).

reference/fleet/example-standalone-monitor-nginx.md

@@ -314,3 +314,4 @@ Congratulations! You have successfully set up monitoring for nginx using standal
 
 * Learn more about [{{fleet}} and {{agent}}](/reference/fleet/index.md).
 * Learn more about [{{integrations}}](integration-docs://reference/index.md).
+* Learn how to manage your [data lifecycle](/manage-data/lifecycle.md).

reference/fleet/manage-integrations.md

@@ -47,15 +47,6 @@ The **Integrations** app in {{kib}} needs access to the public {{package-registr
 
 ::::
 
-
-
-
-
-
-
-
-
-
-
-
-
+:::{tip}
+Once you've started using integrations to ingest data, you can customize how that data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.
+:::

solutions/search/agent-builder/limitations-known-issues.md

@@ -16,12 +16,10 @@ These pages are hidden from the docs TOC and have `noindexed` meta headers.
 
 ## Model selection
 
-Initally, {{agent-builder}} only supports working with the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) running on the Elastic Inference Service which uses Claude Sonnet 3.7, on {{ech}} and {{serverless-full}}. 
+Initially, {{agent-builder}} only supports working with the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) running on the Elastic Inference Service, on {{ech}} and {{serverless-full}}. 
 
 Locally this picks the first AI connector available.
 
-This can be changed under Stack Management -> AI -> GenAI Settings -> Default AI Connector.
-
 ## Known issues
 
 

solutions/search/vector/bring-own-vectors.md

@@ -45,7 +45,7 @@ Each document in our simple data set will have:
 * An embedding of that review: stored in a `review_vector` field, which is defined as a [`dense_vector`](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md) data type.
 
 :::{tip}
-The `dense_vector` type automatically uses quantization by default to reduce the memory footprint when searching float vectors.
+The `dense_vector` type automatically uses quantization to reduce the memory footprint when searching float vectors.
 Learn more about the default quantization strategy and balancing performance and accuracy in [Dense vector field type](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md).
 :::
 

solutions/search/vector/knn.md

@@ -237,10 +237,11 @@ POST byte-image-index/_search
 If you want to provide `float` vectors but still get the memory savings of `byte` vectors, use the [quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) feature. Quantization allows you to provide `float` vectors, but internally they are indexed as `byte` vectors. Additionally, the original `float` vectors are still retained in the index.
 
 ::::{note}
-The default index type for `dense_vector` is `int8_hnsw`.
+The default index type for `dense_vector` is either `bbq_hnsw` or `int8_hnsw`, depending on your product version. Refer to [Dense vector field type](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md).
 ::::
 
-To use quantization, set the `dense_vector` index type to `int8_hnsw` or `int4_hnsw`.
+You can use the default quantization strategy or specify an index option.
+For example, use `int8_hnsw`:
 
 ```console
 PUT quantized-image-index
@@ -291,7 +292,7 @@ PUT quantized-image-index
     }
     ```
 
-Because the original `float` vectors are retained alongside the quantized index, you can use them for re-scoring: retrieve candidates quickly via the `int8_hnsw` (or `int4_hnsw`) index, then rescore the top `k` hits using the original `float` vectors. This provides the best of both worlds, fast search and accurate scoring.
+Because the original `float` vectors are retained alongside the quantized index, you can use them for re-scoring: retrieve candidates quickly via the `int8_hnsw` index, then rescore the top `k` hits using the original `float` vectors. This provides the best of both worlds, fast search and accurate scoring.
 
 ```console
 POST quantized-image-index/_search