Skip to content

[Fleet] Update ilm settings for more uniform rollover/deletion for Fleet files datastreams #98686

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kevinlog
Copy link
Contributor

Update ILM settings for the Fleet files datastreams to have uniform rollover/deletion policies.

Before, the settings were different values ranging from 7d to 90d. This sets them to a uniform deletion of 7d

@elasticsearchmachine elasticsearchmachine added the external-contributor Pull request authored by a developer outside the Elasticsearch team label Aug 21, 2023
@kevinlog kevinlog added :Security/Security Security issues without another label and removed external-contributor Pull request authored by a developer outside the Elasticsearch team labels Aug 21, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@kevinlog kevinlog added the >bug label Aug 21, 2023
@elasticsearchmachine elasticsearchmachine added the Team:Security Meta label for security team label Aug 21, 2023
@kevinlog kevinlog requested a review from pzl August 21, 2023 16:50
@kevinlog kevinlog marked this pull request as draft August 21, 2023 17:01
@ywangd
Copy link
Member

ywangd commented Aug 22, 2023

I think the change is more relevant to the @elastic/es-data-management team instead of security. So I am tagging them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Data Management/ILM+SLM Index and Snapshot lifecycle management :Security/Security Security issues without another label Team:Fleet Team:Security Meta label for security team v8.10.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants