apm-data: increase priority above Fleet templates #108885
Merged
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.
Fleet installs templates with a priority of either 150 or 200, documented to be anything between 100 and 200, per https://www.elastic.co/guide/en/elasticsearch/reference/current/index-templates.html.
We now want the apm-data templates to take precedence over the ones installed by the integration package, so we increase their priority to 210.
Relates to elastic/apm-server#11528