dev_doc: add evolution of index management #16685
Open
Conversation
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
|
This pull request does not have a backport label. Could you fix it @rubvs? 🙏
|
rubvs
force-pushed
the
doc-index-management
branch
from
9eed965 to
b456a58
Compare
simitt
requested changes
Apr 22, 2025
carsonip
reviewed
Apr 22, 2025
carsonip
reviewed
Apr 22, 2025
simitt
requested changes
Apr 30, 2025
|
|
||
| The switch to the ES apm plugin caused several issues for our customers, see [Elastic APM Known Issues](https://www.elastic.co/docs/release-notes/apm/known-issues). | ||
|
|
||
| - **Sep 16, 2024 (v8.16.0)** |
There was a problem hiding this comment.
The below fixes do not all belong to 8.16.0, and you list a version for every point, so I'd remove this header.
There was a problem hiding this comment.
Related to my comment above: #16685 (comment)
| - PR [#116219](https://github.com/elastic/elasticsearch/pull/116219) will trigger a lazy rollover of existing data streams regardless of whether the index template is being created or updated. | ||
| - This ensures that the apm-data plugin will roll over data streams that were previously using the Fleet integration package. | ||
| - **Nov 13, 2024 (v8.17.0)** | ||
| - With the new index templates, if you were not using any custom ILM Policy, APM data will obey to the new Data stream Lifecycle instead of ILM. |
There was a problem hiding this comment.
In 8.17.0 DSL was removed, it's always ILM going forward. What made you think it is still DSL for the default case?
| - This ensures that the apm-data plugin will roll over data streams that were previously using the Fleet integration package. | ||
| - **Nov 13, 2024 (v8.17.0)** | ||
| - With the new index templates, if you were not using any custom ILM Policy, APM data will obey to the new Data stream Lifecycle instead of ILM. | ||
| - The default ILM Policies of APM are removed if not in use. If you defined a custom ILM policy via a `@custom` component template, the ILM policy will be preserved and preferred to DSL. |
There was a problem hiding this comment.
Default ILM policies are not removed.
| - **Nov 13, 2024 (v8.17.0)** | ||
| - With the new index templates, if you were not using any custom ILM Policy, APM data will obey to the new Data stream Lifecycle instead of ILM. | ||
| - The default ILM Policies of APM are removed if not in use. If you defined a custom ILM policy via a `@custom` component template, the ILM policy will be preserved and preferred to DSL. | ||
| - In [#115687](https://github.com/elastic/elasticsearch/pull/115687), we moved to adding default ILM policies and switch to ILM for apm-data plugin, instead of just having a fallback as outlined in [#112759](https://github.com/elastic/elasticsearch/pull/112759). |
There was a problem hiding this comment.
The apm-data plugin is used for apm-server and for serverless; maybe this caused some confusion on some of the PRs.
| - **May 26, 2024 (v8.15.0)** | ||
| - In [#9949](https://github.com/elastic/integrations/pull/9949) all datastreams was removed from APM Integrations. | ||
|
|
||
| ### 8.x - (Fixes & Improvements) |
There was a problem hiding this comment.
I find the timelines below confusing as it is right now.
@lahsivjar given that you worked on several of the PRs, could you help add some clarification and give this a sanity check?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #14177
Add an overview and timeline for the evolution of index management in APM Server.