[EventLog] change to use Data stream lifecycle instead of ILM #163210
Conversation
This file contains 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
pmuellr
added
release_note:enhancement
Team:ResponseOps
|
Documentation preview: |
The default continues to be 90 days for data detetention of event log documents, and the rollover is now controlled by DLM, as described in [Data stream lifecycle][]. [Data stream lifecycle]: https://www.elastic.co/guide/en/elasticsearch/reference/8.9/data-stream-lifecycle.html Fixes the event log data stream to use Data stream lifecycle instead of Index Lifecycle Management. If you had previously customized the Kibana event log ILM policy, you should now update the lifecycle of the event log data stream itself.
pmuellr
force-pushed
the
162886-event-log-dlm
branch
from
7214436
to
36321a4
Compare
|
Pinging @elastic/response-ops (Team:ResponseOps) |
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
kibanamachine
added
v8.10.0
backport:skip
bryce-b
pushed a commit
to bryce-b/kibana
that referenced
this pull request
Aug 9, 2023
…c#163210) resolves elastic#162886 The default continues to be 90 days for data detetention of event log documents, and the rollover is now controlled by DLM, as described in [Data stream lifecycle][]. [Data stream lifecycle]: https://www.elastic.co/guide/en/elasticsearch/reference/8.9/data-stream-lifecycle.html ## Release note Fixes the event log data stream to use Data stream lifecycle instead of Index Lifecycle Management. If you had previously customized the Kibana event log ILM policy, you should now update the lifecycle of the event log data stream itself.
pmuellr
added a commit
to pmuellr/kibana
that referenced
this pull request
Aug 23, 2023
…elastic#163210)" This reverts commit 7e234b1.a The commit came from PR elastic#163210 See elastic#164581 for the issue the original PR caused.
pmuellr
added a commit
that referenced
this pull request
Aug 24, 2023
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.
resolves #162886
The default continues to be 90 days for data detetention of event log documents, and the rollover is now controlled by DLM, as described in Data stream lifecycle.
Release note
Fixes the event log data stream to use Data stream lifecycle instead of Index Lifecycle Management. If you had previously customized the Kibana event log ILM policy, you should now update the lifecycle of the event log data stream itself.
Checklist
Delete any items that are not applicable to this PR.