-
Notifications
You must be signed in to change notification settings - Fork 525
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
[docs] Document how to customize index settings and ILM policies for managed apm-server #5988
Comments
Should we document this under: https://www.elastic.co/guide/en/apm/guide/current/apm-tune-elasticsearch.html ? The custom component template names are fixed right? We can just document the |
@Mpdreamz We have custom ILM docs in that bucket already: https://www.elastic.co/guide/en/apm/guide/8.0/ilm-how-to.html. AFAIK though, the edits to These are the issues I'm tracking:
We've also paused docs for custom ingest pipelines: elastic/observability-docs#1226. |
Setting custom ILM policies that are persisted between updates is supposed to be working. elastic/kibana#111197 moved the |
Silvia is right. I misunderstood elastic/kibana#121184. I'll close this issue as documentation already exists in 7.17+ for custom APM ILM. |
By default, an empty custom component template is created per data stream. If users want to change index settings and/or ILM policies they can use these component templates for any customization. Custom templats are not overwritten on upgrade.
GET _index_template/<data-stream>
to identify the custom component template name (composed_of
)GET _component_template/t<custom-component-name>
to retrieve custom component template settingsPUT _component_template/t<custom-component-name>
to update it, for example:Document that default ILM policies might be changed within minor version upgrades. This is not considered a breaking change, but helps to continually improve and adapt the index management to new features and requirements. If users want to avoid any surprises, they are supposed to make use of setting up a custom ILM policy.
The text was updated successfully, but these errors were encountered: