Merge branch 'main' into add-elastic-new-intro-section

Author: theletterf

deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md

@@ -73,6 +73,10 @@ Elastic manages the installation and configuration of the monitoring agent for y
 - Enabling logging and monitoring increases the resource consumption of the deployment. For production systems, we recommend sizing deployments with logging and monitoring enabled to at least 4 GB of RAM on each {{es}} instance.
 - Enabling logging and monitoring can trigger a plan change on your deployment. You can monitor the plan change progress from the deployment's **Activity** page.
 
+:::{tip}
+The monitoring deployment and production deployment must be on the same major version, cloud provider, and region.
+:::
+
 To enable monitoring on your deployment:
 
 :::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md
@@ -147,8 +151,8 @@ The `*` indicates that we also index the archived files of each type of log.
 Check the respective product documentation for more information about the logging capabilities of each product.
 
 ## Restrictions and limitations [restrictions-monitoring]
-
+* The monitoring deployment and production deployment must be on the same major version, cloud provider, and region.
 * To avoid compatibility issues, ensure your monitoring cluster and production cluster run on the same {{stack}} version. Monitoring clusters that use 9.x do work with production clusters that use the latest release of 8.x, but this setup should only occur when upgrading clusters to the same version.
 * $$$cross-region-monitor$$$ Monitoring across regions is not supported. If you need to move your existing monitoring to the same region, you can do a reindex or create a new deployment and select the snapshot from the old deployment.
 * The logs shipped to a monitoring cluster use an ILM managed data stream (`elastic-cloud-logs-<version>`). If you need to delete indices due to space, do not delete the current `is_write_enabled: true` index.
-* When sending metrics to a dedicated monitoring deployment, the graph for IO Operations Rate(/s) is blank. This is due to the fact that this graph actually contains metrics from of all of the virtualized resources from the provider.
+* When sending metrics to a dedicated monitoring deployment, the graph for IO Operations Rate(/s) is blank. This is due to the fact that this graph actually contains metrics from of all of the virtualized resources from the provider.

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

@@ -8,20 +8,21 @@ products:
 
 # Manually apply a lifecycle policy to an index [apply-policy-manually]
 
-When you create a new {{es}} index, it automatically picks up settings, mappings, and aliases from any matching [index template](/manage-data/data-store/templates.md#index-templates) and its component templates. If the template specifies a lifecycle policy, that policy is applied to the new index as soon as it's created. This process is described in detail in [Configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md).
+When you create a new {{es}} index, it automatically picks up settings, mappings, and aliases from any matching [index template](/manage-data/data-store/templates.md#index-templates) and its component templates. If the template specifies a lifecycle policy, that policy is applied to the new index as soon as it's created so that the index will be managed by {{ilm-init}}. This process is described in detail in [Configure a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md).
 
-You can also apply a lifecycle policy manually to existing indices, as described on this page. This is useful if you want to:
+You can also apply a lifecycle policy manually to existing indices that are not yet managed, as described on this page. This is useful if you want to:
  * Configure the indices to move through different [data tiers](/manage-data/lifecycle/data-tiers.md) as they age.
  * Perform [lifecycle actions](elasticsearch://reference/elasticsearch/index-lifecycle-actions/index.md) such as downsampling or shrinking.
  * Delete the indices when they reach a certain age.
 
-If an index is currently managed by an ILM policy you must first remove that policy before applying a new one. Refer to [Switch to a different lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/policy-updates.md#switch-lifecycle-policies) for details.
+:::{warning}
+Consider the following before manually applying a policy to an index:
 
-You can do this procedure in {{kib}} or using the {{es}} API.
+* If an index is currently managed by an ILM policy you must first remove that policy before applying a new one. To remove or make changes to an {{ilm-init}} policy currently applied to one or more indices, or to switch indices to use a different policy, refer to [Update or switch a lifecycle policy](/manage-data/lifecycle/index-lifecycle-management/policy-updates.md).
+* Do not manually apply a policy that uses the rollover action. Policies that use rollover must be applied by the [index template](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template). Otherwise, the policy is not carried forward when the rollover action creates a new index.
+:::
 
-::::{warning}
-Do not manually apply a policy that uses the rollover action. Policies that use rollover must be applied by the [index template](/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md#apply-policy-template). Otherwise, the policy is not carried forward when the rollover action creates a new index.
-::::
+You can do this procedure in {{kib}} or using the {{es}} API.
 
 ::::{tab-set}
 :group: kibana-api

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

@@ -1,5 +1,4 @@
 ---
-navigation_title: Update or switch a policy
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/update-lifecycle-policy.html
 applies_to:
@@ -10,13 +9,13 @@ products:
 
 # Update or switch a lifecycle policy
 
-
 You can change how the lifecycle of an index or collection of rolling indices is managed by modifying the current policy or switching to a different policy.
 
 To ensure that policy updates don’t put an index into a state where it can’t exit the current phase, the phase definition is cached in the index metadata when it enters the phase. If changes can be safely applied, {{ilm-init}} updates the cached phase definition. If they cannot, phase execution continues using the cached definition.
 
 When the index advances to the next phase, it uses the phase definition from the updated policy.
 
+To configure an index not currently managed by {{ilm-init}} to be governed by an lifecycle policy, refer to [Manually apply a policy to an index](/manage-data/lifecycle/index-lifecycle-management/policy-apply.md).
 
 ## How changes are applied [ilm-apply-changes]
 

release-notes/elastic-cloud-serverless/index.md

@@ -294,6 +294,7 @@ Review the changes, fixes, and more to {{serverless-full}}.
 * Enables custom roles by default [#227878]({{kib-pull}}227878)
 * Allows submitting case comments by pressing **⌘+Enter** (or **Ctrl+Enter**) [#228473]({{kib-pull}}228473)
 * Increases the number of supported **Group by** fields in threshold rules from 3 to 5 [#227465]({{kib-pull}}227465)
+* Adds the **Search AI Lake** view to AutoOps for {{serverless-full}} to provide storage usage insights
 
 ### Fixes [serverless-changelog-07222025-fixes]
 
@@ -362,6 +363,7 @@ Review the changes, fixes, and more to {{serverless-full}}.
 * Uses `id` instead of `name` to group vulnerabilities by resource and cloud account in {{sec-serverless}} [#225492]({{kib-pull}}225492)
 * Updates Gemini model in {{sec-serverless}} [#225917]({{kib-pull}}225917)
 * Updates the navigation menu in {{es-serverless}} [#225709]({{kib-pull}}225709)
+* Adds performance charts to the **Usage and performance** section on the project overview page in {{serverless-full}}
 
 
 ### Fixes [serverless-changelog-07072025-fixes]