From b0025f23d6c0ae79e59ff3d4d54274f6fb5eaea7 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Fri, 8 Nov 2024 19:36:21 +0000 Subject: [PATCH] Raise prefer_ilm configuration as a known issue (#4505) (#4512) * Raise prefer_ilm configuration as a known issue * Fix link * Update docs/en/observability/apm/known-issues.asciidoc * Update docs/en/observability/apm/known-issues.asciidoc Co-authored-by: Brandon Morelli * Update docs/en/observability/apm/known-issues.asciidoc Co-authored-by: Brandon Morelli --------- Co-authored-by: Brandon Morelli (cherry picked from commit c24c557aa5db537d47e1a6462286b8977e7b9fba) Co-authored-by: Vishal Raj --- .../observability/apm/known-issues.asciidoc | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/en/observability/apm/known-issues.asciidoc b/docs/en/observability/apm/known-issues.asciidoc index 72f8990b39..6d7af2ebd5 100644 --- a/docs/en/observability/apm/known-issues.asciidoc +++ b/docs/en/observability/apm/known-issues.asciidoc @@ -21,6 +21,28 @@ _Versions: XX.XX.XX, YY.YY.YY, ZZ.ZZ.ZZ_ // If applicable, link to fix //// +[discrete] +== `prefer_ilm` required in component templates to create custom lifecycle policies + +_Elastic Stack versions: 8.15.1+_ + +// The conditions in which this issue occurs +The issue occurs when creating a _new_ cluster using version 8.15.1+. +The issue occurs for any APM data streams created in 8.15.1+. +The issue does _not_ occur if custom component template has been created in or before version 8.15.0. + +// Describe why it happens +In 8.15.0, APM Server began using the https://github.com/elastic/elasticsearch/tree/main/x-pack/plugin/apm-data[apm-data plugin] +to manage data streams, ingest pipelines, lifecycle policies, and more. In 8.15.1, a fix was introduced to address +unmanaged indices in older clusters using default ILM policies. This fix added a fallback to the default ILM policy +(if it exists) and set the `prefer_ilm` configuration to `false`. This setting impacts clusters where both ILM and +data stream lifecycles (DSL) are in effect—such as when configuring custom ILM policies using `@custom` component +templates, under the conditions mentioned above. + +// How to fix it +To override ILM policies for these new clusters using component template, set the `prefer_ilm` configuration +to `true` by following the {observability-guide}/apm-ilm-how-to.html[updated guide to customize ILM]. + [discrete] == Upgrading to v8.15.x may cause ingestion to fail