-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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.
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
x-pack/plugin/apm-data: fix @custom
component templates
#104182
x-pack/plugin/apm-data: fix @custom
component templates
#104182
Conversation
Use `<data_stream.type>@custom` instead of `apm@custom`. This is an enhancement over what Fleet sets up; it is an additive improvement in the direction of elastic#97664. The rollup data streams' `@custom` component templates now include the duration, like what Fleet sets up. Add a YAML REST test, and a unit test ensuring consistency across the index templates.
Hi @axw, I've created a changelog YAML for you. |
@custom
component templates@custom
component templates
Pinging @elastic/es-data-management (Team:Data Management) |
I'm wondering if we should keep the |
@felixbarny |
Ah, I wasn't aware of that. Makes sense then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love the test chat checks for compliance to the naming conventions
@elasticmachine update branch |
Use
<data_stream.type>@custom
instead ofapm@custom
. This is an enhancement over what Fleet sets up; it is an additive improvement in the direction of #97664.The rollup data streams'
@custom
component templates now include the duration, like what Fleet sets up.Add a YAML REST test, and a unit test ensuring consistency across the index templates.