From 059e820cfec2356d11ff92302dc1dba415650938 Mon Sep 17 00:00:00 2001 From: Roberto Seldner Date: Mon, 3 Nov 2025 11:30:06 -0700 Subject: [PATCH 1/2] Update instructions for setting retention policies replaced outdated/legacy references since logging and metrics start using datastreams in 3.8. There is room for improvement but kept it simple for now. --- .../orchestrators/ece-monitoring-ece-set-retention.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md index 972d55b5f1..4bca37f43e 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md @@ -20,7 +20,7 @@ You might need to adjust the retention period for one of the following reasons: To customize the retention period, set up a custom lifecycle policy for logs and metrics indices: 1. [Create a new index lifecycle management (ILM) policy](../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) in the logging and metrics cluster. -2. Create a new, legacy-style, index template that matches the data view (formerly *index pattern*) that you want to customize the lifecycle for. -3. Specify a lifecycle policy in the index template settings. -4. Choose a higher `order` for the template so the specified lifecycle policy will be used instead of the default. +2. Create a new composable index template that matches the data view (formerly *index pattern*) for the datastream you want to customize the lifecycle for. +3. Specify a custom lifecycle policy in the index template settings. +4. Choose a higher `priority` for the template so the specified lifecycle policy will be used instead of the default. From 6c4457d28325dd826d5c71d440d5ba355d1ac47a Mon Sep 17 00:00:00 2001 From: Roberto Seldner Date: Mon, 3 Nov 2025 14:15:32 -0700 Subject: [PATCH 2/2] Update deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md thanks! Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- .../monitor/orchestrators/ece-monitoring-ece-set-retention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md index 4bca37f43e..f106db2a59 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md @@ -20,7 +20,7 @@ You might need to adjust the retention period for one of the following reasons: To customize the retention period, set up a custom lifecycle policy for logs and metrics indices: 1. [Create a new index lifecycle management (ILM) policy](../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) in the logging and metrics cluster. -2. Create a new composable index template that matches the data view (formerly *index pattern*) for the datastream you want to customize the lifecycle for. +2. Create a new composable index template that matches the data view (formerly *index pattern*) for the data stream you want to customize the lifecycle for. 3. Specify a custom lifecycle policy in the index template settings. 4. Choose a higher `priority` for the template so the specified lifecycle policy will be used instead of the default.