Skip to content
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

[Index Management] Update data retention time unit options #168495

Closed
Tracked by #154256
alisonelizabeth opened this issue Oct 10, 2023 · 1 comment · Fixed by #168560
Closed
Tracked by #154256

[Index Management] Update data retention time unit options #168495

alisonelizabeth opened this issue Oct 10, 2023 · 1 comment · Fixed by #168560
Assignees
Labels
enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@alisonelizabeth
Copy link
Contributor

We should consider hiding the following time units in the UI:

  • nanoseconds
  • microseconds
  • milliseconds
Screenshot 2023-10-10 at 11 29 00 AM

Note: These units are still technically allowed via the API. In order provide backwards compatability, we should show the time units above only IF it was previously configured that way.

@alisonelizabeth alisonelizabeth added enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Oct 10, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants