-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Upgrade Assistant] Handle migration of legacy APM indices #91875
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
By default apm-server indexes data into indices matching In addition to checking the index name, we should probably search on |
@alisonelizabeth FYI, I've just merged a change in apm-server to introduce a new ingest pipeline called |
Great! Thanks @axw. I will likely follow-up with you with questions once I'm able to start working on this. |
@axw and I chatted about this over Slack on August 25. Andrew informed me that at the time the team wasn't sure if they'd need support for upgrading/reindexing indices to data streams in 8.0. APM UI will continue to read indices in 8.0 instead of introducing a hard break, but it's currently unclear how far into the future they'll extend that support. We agreed to defer working on this until they have more clarity on this. |
no longer relevant |
This work is necessary for the 7.x-8 upgrade.This work has been deferred to 8.x. The below information might be partially or completely obsolete.Background
APM Server is undergoing some fairly significant changes over the next few 7.x releases, moving from being a standalone service to one that runs under Fleet. As part of that effort we are migrating to use data streams instead of raw indices. We also anticipate some breaking changes to the schema, e.g. combining multiple numerical fields into a single aggregate_metric_double field.
For the remainder of 7.x there will be the option to use either indices or data streams, but in 8.0 we will require Fleet and data streams will be the only option. In 8.0, the APM app in Kibana will query only the new data streams. Because only the new data streams will be queried, we should provide an option for users to migrate their old data.
Requirements
The Upgrade Assistant will need to provide a means of reindexing old data (similar to the 6-7 upgrade):
The text was updated successfully, but these errors were encountered: