Describe the feature:
We plan to add support for maximum and default retention for data stream lifecycles inside of Elasticsearch. We'd also like to have support for these values on the UI side. There are multiple pieces of work for this:
A UI on the Project creation/editing page that will let the user set these while the project is being created
A way to return to the UI from within Kibana if the user wants to edit the values after a project/cluster is created
A warning if the user attempts to set a data stream's lifecycle retention to a value higher than the configured maximum
Displaying the effective retention for a data stream (we don't yet know exactly how ES will expose this)
Instructions for how to configure these cluster settings for on-prem and ESS clusters if a user would like to modify them.
Describe a specific use case for the feature:
Certain teams would like an administrator to be able to configure a maximum retention for all data to ensure compliance. Additionally, they'd like to configure a default value for retention so that integrations can be added to the system without having to manually configure each one to a certain retention value.
Describe the feature: We plan to add support for maximum and default retention for data stream lifecycles inside of Elasticsearch. We'd also like to have support for these values on the UI side. There are multiple pieces of work for this:
Describe a specific use case for the feature: Certain teams would like an administrator to be able to configure a maximum retention for all data to ensure compliance. Additionally, they'd like to configure a default value for retention so that integrations can be added to the system without having to manually configure each one to a certain retention value.