Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add reference to prefer-ilm setting for apm lifeycle known bug #4501

Merged
merged 6 commits into from
Nov 8, 2024
Merged

Add reference to prefer-ilm setting for apm lifeycle known bug #4501

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f2eec04
Add reference to prefer-ilm setting for apm lifeycle known bug
lahsivjar Nov 8, 2024
b6e7c70
Refactor
lahsivjar Nov 8, 2024
3de4736
APM known issue correction
inge4pres Nov 8, 2024
d226ee9
Update docs/en/observability/apm/known-issues.asciidoc
bmorelli25 Nov 8, 2024
ef8f699
clean up text
bmorelli25 Nov 8, 2024
37b338c
Update docs/en/observability/apm/known-issues.asciidoc
bmorelli25 Nov 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/en/observability/apm/known-issues.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,10 @@ used. One of the following approaches can be adopted to fix the unmanaged indice
. Manually delete the indices when they are no longer needed.
. Explicitly configure APM data streams with the default data stream lifecycle config.
Using this approach would migrate all data streams to use data stream lifecycles,
which should be equivalent to the default ILM policies:
which should be equivalent to the default ILM policies. Note that if you have a custom
lifecycle policy in place for any of the datastreams then you don't need to do anything
for those datastreams as they are not affected by this bug. Going forward, for using
custom ILM policies with new datastreams, please consult the {ref}/apm-ilm-how-to.html[updated guide].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you think this belongs here? If I have a custom ILM policy I don't even read this line due to

The issue also does not occur if a custom ILM policy is configured using a custom component template.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took a stab at updating this in a different way to avoid confusion. PTAL.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part looks good to me now - are you planning on also adding the prefer-ilm section to this PR or a separate one? (The PR description is not updated)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created a separate PR for that: https://github.com/elastic/observability-docs/pull/4505/files

+
[source,txt]
----
Expand Down
Loading