Update title for the built-in ILM policies customization topic #3647
Conversation
Fixes #3285 to clarify that the scope of the tutorial refers to Elastic Agent data streams that use built-in ILM policies.
yetanothertw
added
documentation
| --- | ||
|
|
||
| # Customize built-in policies | ||
| # Customize built-in {{ilm-init}} policies for {{agent}} data streams |
There was a problem hiding this comment.
stated scope conflicts a little with some of the xrefs. this one just says agent data streams, but we also have the following scopes indicated on the other pages you edited:
- {{beats}}, {{agent}}, or for the {{agent}} or {{ls}} {{es}} output plugin managed data streams
- Elastic integration managed data streams
maybe this should become managed data streams and the fleet info on this page might pivot to a "for example" framing
accuracy on all of this I'm not certain on - just looking at signals I'm seeing within this doc :)
There was a problem hiding this comment.
might be worth doing a dive to find the context in which those two contexts were added to clarify
There was a problem hiding this comment.
Good point. Seems like the title describes well the use case in the tutorial, but doesn't account for use cases mentioned in the topics that link to it.
I'll find someone to validate this with and make some changes.
2 participants
Fixes #3285 to clarify that the scope of the tutorial refers to Elastic Agent data streams that use built-in ILM policies.