Doc: Use index with/out datemath OR alias/datastream#1252
Open
karenzone wants to merge 2 commits intologstash-plugins:mainfrom
Open
Doc: Use index with/out datemath OR alias/datastream#1252karenzone wants to merge 2 commits intologstash-plugins:mainfrom
karenzone wants to merge 2 commits intologstash-plugins:mainfrom
Conversation
karenzone
changed the title
karenzone
changed the title
stefnestor
reviewed
Mar 25, 2026
| Time-based routing in this plugin follows *one* model at a time. _Do not_ mix models. | ||
|
|
||
| * *Data streams.* Use <<plugins-{type}s-{plugin}-data_stream,`data_stream`>> and related settings. | ||
| * *Index lifecycle management (ILM) rollover.* The value you set using <<plugins-{type}s-{plugin}-ilm_pattern,`ilm_pattern`>> is used for naming, and should align with {ref}/indices-rollover-index.html#_using_date_math_with_the_rollover_api[Elasticsearch rollover naming]. |
There was a problem hiding this comment.
Data streams can use ILM or DLM. The callout is alias.
Contributor
Author
There was a problem hiding this comment.
Thanks for the clarification, @stefnestor. Please put the change you'd like to see in as a suggestion.
There was a problem hiding this comment.
Uh, sorry. 🙈. I'm feeling unhelpful in you trying to help me. Starting with what you said already but said way worse:
Time-based routing in this plugin allows *one* target model at a time: data stream, alias, or index.
_Do not_ mix models. Data stream supports ILM+DLM. Aliases support ILM. Index supports ILM
but not ILM rollover.
Note `index` stands for an ingest target. It allows dynamic content via placeholders `%{...}`, such
as date math. Placeholders might make sense with data streams and aliases, but results should be
validated against cluster index templates and ILM setup. Placeholder date math should not normally
be used with aliases nor data streams.
stefnestor
reviewed
Mar 25, 2026
|
|
||
| * *Data streams.* Use <<plugins-{type}s-{plugin}-data_stream,`data_stream`>> and related settings. | ||
| * *Index lifecycle management (ILM) rollover.* The value you set using <<plugins-{type}s-{plugin}-ilm_pattern,`ilm_pattern`>> is used for naming, and should align with {ref}/indices-rollover-index.html#_using_date_math_with_the_rollover_api[Elasticsearch rollover naming]. | ||
| * *Explicit index names.* Use the <<plugins-{type}s-{plugin}-index,`index`>> setting and `%{+...}` syntax for daily (or other) rotation. |
There was a problem hiding this comment.
I really appreciate your help & don't mean to be pedantic, but I think "explicit" index name indicates static vs date math rotation is still a form of implicit naming convention 🙃.
Contributor
Author
|
cc:/ FYI @robbavey for your and your team |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves: elastic/docs-content#2761
Test is here:
DocTest - elasticsearch-output - DO NOT MERGE#2038