-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[DOC+][ILM][Troubleshooting] JQ for transient steps #99612
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
Conversation
👋 howdy, team! Can we add these common JQ queries to the [ILM Troubleshooting Doc](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-error-handling.html) which check for indices not in "waiting" steps (as defined by Stef) of `[complete, check-rollover-ready]` and defining them as expectedly "transient" steps. Is helpful until/unless #93859
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-data-management (Team:Data Management) |
DaveCTurner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The trouble with docs like this is that they aren't covered by tests so will fall out of date in time without anybody noticing. If these things are useful, let's include them in the ILM explain output directly.
Co-authored-by: David Turner <david.turner@elastic.co>
|
@DaveCTurner does this look good to merge? (Noted on pushing this type of data into ILM overview / ES internal health longer-term.) |
|
No - these commands need test coverage to avoid them going stale over time. I think the easiest way to achieve that will be to add these things to the ILM explain API, but maybe there are other ways if we really want to have |
|
I think we can close this, since we discussed it and decided adding columns to the cat indices would be a better solution. |
|
👋 @dakrone @DaveCTurner I would still prefer an aggregated summary on how ILM indices are doing if possible. Maybe my team's just used to the JQ query if we'd reconsider it. Alternatively, It looks like some ES Diags on more recent versions also have an |
|
That is the ILM indicator of the health report API, which is documented at https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html#health-api-response-details-ilm |
|
As follow-up to ongoing troubleshooting pain points of not documenting this JQ command
|
👋 howdy, team!
Can we add these common JQ queries to the ILM Troubleshooting Doc which check for indices not in "waiting" steps (as defined by me) of
[complete, check-rollover-ready]and claiming the rest are "transient" steps.Will still be helpful even after #93859 .