From 9ee7d76504b61f9b8ae235a4bdea1d086be7580c Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Fri, 29 Aug 2025 11:35:29 -0400 Subject: [PATCH] [Fleet] Fix note formatting for cloned templates --- reference/fleet/data-streams-scenario3.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/reference/fleet/data-streams-scenario3.md b/reference/fleet/data-streams-scenario3.md index 8f4f34d20c..499cc220e7 100644 --- a/reference/fleet/data-streams-scenario3.md +++ b/reference/fleet/data-streams-scenario3.md @@ -78,9 +78,10 @@ metrics-system.network-production@custom Now that you’ve created a component template, you need to create an index template to apply the changes to the correct data stream. The easiest way to do this is to duplicate and modify the integration’s existing index template. ::::{warning} -Note the following: * When duplicating the index template, do not change or remove any managed properties. This may result in problems when upgrading. Cloning the index template of an integration package involves some risk as any changes made to the original index template when it is upgraded will not be propagated to the cloned version. * These steps assume that you want to have a namespace specific ILM policy, which requires index template cloning. Cloning the index template of an integration package involves some risk because any changes made to the original index template as part of package upgrades are not propagated to the cloned version. See [Cloning the index template of an integration package](/reference/fleet/integrations-assets-best-practices.md#assets-restrictions-cloning-index-template) for details. +- If you duplicate an index template, do not change or remove any managed properties. This may result in problems when upgrading. Cloning the index template of an integration package involves some risk as any changes made to the original index template are not propagated to the cloned version when you upgrade versions. +- These steps assume that you want to have a namespace specific ILM policy, which requires index template cloning. Cloning the index template of an integration package involves some risk because any changes made to the original index template as part of package upgrades are not propagated to the cloned version. Check out [Cloning the index template of an integration package](/reference/fleet/integrations-assets-best-practices.md#assets-restrictions-cloning-index-template) for details. -+ If you want to change the ILM Policy, the number of shards, or other settings for the datastreams of one or more integrations, but **the changes do not need to be specific to a given namespace**, it’s strongly recommended to use a `@custom` component template, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md), so as to avoid the problems mentioned above. See the [ILM](/reference/fleet/data-streams.md#data-streams-ilm) section for details. ++ If you want to change the ILM Policy, the number of shards, or other settings for the datastreams of one or more integrations, but **the changes do not need to be specific to a given namespace**, use a `@custom` component template, as described in [Scenario 1](/reference/fleet/data-streams-scenario1.md) and [Scenario 2](/reference/fleet/data-streams-scenario2.md), to avoid the problems mentioned earlier. Check out the [ILM](/reference/fleet/data-streams.md#data-streams-ilm) section for details. ::::