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

[ILM] Put "Retry lifecycle step" button directly inside of error callout in Index Management #27159

Open
cjcenizal opened this issue Dec 13, 2018 · 2 comments
Labels
Feature:ILM good first issue low hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@cjcenizal
Copy link
Contributor

When there's a lifecycle error, a common solution is to retry the lifecycle step by clicking this option under the "Actions" menu. It would be a nice UX improvement to show the user this button directly inside of the error callout.

@cjcenizal cjcenizal added Feature:ILM Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels Dec 13, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui

@yuliacech
Copy link
Contributor

Index Lifecycle Management (ILM) plugin uses an extension service provided by Index Management (IM) plugin to add a banner to Indices list in IM. This banner is shown when any index has an ILM step error and currently includes a filter for the search bar. We could update extension service to also accept a button handler for the callout. The function to retry an ILM step by clicking an option in 'Actions' menu is being added to IM via the extension service as well.

@yuliacech yuliacech added the good first issue low hanging fruit label Apr 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:ILM good first issue low hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

3 participants