-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Add HLRC docs for Explain LIfecycle #35803
Merged
gwbrown
merged 3 commits into
elastic:master
from
gwbrown:ilm/hlrc-explain-lifecycle-docs
Nov 26, 2018
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
-- | ||
:api: ilm-explain-lifecycle | ||
:request: ExplainLifecycleRequest | ||
:response: ExplainLifecycleResponse | ||
-- | ||
|
||
[id="{upid}-{api}"] | ||
=== Explain Lifecycle API | ||
|
||
|
||
[id="{upid}-{api}-request"] | ||
==== Request | ||
|
||
The Explain Lifecycle API allows you to retrieve information about the execution | ||
of a Lifecycle Policy with respect to one or more indices. | ||
|
||
["source","java",subs="attributes,callouts,macros"] | ||
-------------------------------------------------- | ||
include-tagged::{doc-tests-file}[{api}-request] | ||
-------------------------------------------------- | ||
<1> Requests an explanation of policy execution for `my_index` and `other_index` | ||
|
||
|
||
[id="{upid}-{api}-response"] | ||
==== Response | ||
|
||
The returned +{response}+ contains a map of `LifecyclePolicyMetadata`, | ||
accessible by the name of the policy, which contains data about each policy, | ||
as well as the policy definition. | ||
|
||
["source","java",subs="attributes,callouts,macros"] | ||
-------------------------------------------------- | ||
include-tagged::{doc-tests-file}[{api}-response] | ||
-------------------------------------------------- | ||
<1> The name of the policy in use for this index, if any. | ||
<2> Indicates whether this index is being managed by Index Lifecycle Management. | ||
<3> The Phase (`hot`, `warm`, etc.) this index is currently in. | ||
<4> The time this index entered this Phase of execution. | ||
<5> The Action (`rollover`, `shrink`, etc.) this index is currently in. | ||
<6> The Step this index is currently in. | ||
<7> If this index is in the `ERROR` Step, this will indicate which Step failed. | ||
|
||
include::../execution.asciidoc[] | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
we should add the example response for
otherIndex
here tooThere 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.
I'm not sure what would be different in terms of what we show here - it will just have different values (
isManaged = false
, everything else is null), which we don't show in the docs. Do you just mean we should addindices.get("other_index")
to show that you can do it?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.
I was thinking of adding anchored comments discussing how things will be null or something. Maybe adding it in the description?
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.
Yeah, with adding it to the description makes more sense to me - I'll also add some asserts to that effect.
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.
👍