-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[DOCS] Edit ILM GS tutorial #51513
[DOCS] Edit ILM GS tutorial #51513
Conversation
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
Pinging @elastic/es-docs (>docs) |
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.
Thanks for working on this @debadair
I think this will be a great improvement and it'll help make the "join the ilm train" experience smoother.
I've left a few suggestions below.
. <<ilm-gs-check-progress, Verify that indexes are moving through the lifecycle phases>> as expected with the | ||
you use the {ilm-init} explain API. |
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.
"with the explain API"
<1> The `min_age` field defaults to `0ms` in the hot phase, so new indices immediately enter the hot phase. | ||
<2> The `rollover` action is triggered when any of the conditions are met. | ||
<3> An index is moved into the delete phase after 90 days. | ||
<4> No additional conditions are specified, so the `delete` action is triggered when the index enters the delete phase. |
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 delete action doesn't support any conditionals/parameters so I think we shouldn't mention conditionals here but rather "The delete action is triggered ..."
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.
Fixed.
@elasticmachine update branch |
merge conflict between base and head |
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.
Thanks for iterating on this @debadair. This is great! There's one typo in the index name , but other than that LGTM
|
||
For example, the following request creates an index called `datastream_000001` |
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.
datastream_000001
-> datastream-000001
|
||
When you continuously index timestamped documents into {es} using | ||
Filebeat, Logstash, or some other mechanism, | ||
you typically use an index alias so you can periodically roll over to a new index. |
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.
Link for index alias?
|
||
To begin, we will want to bootstrap our first index to write to. | ||
To get things started, you need to bootstrap an initial index and |
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.
To get things started, you need to bootstrap an initial index and | |
To get things started, you need to create an initial index and |
|
||
* Creates a new index called `datastream-000002`. | ||
This matches the `datastream-*` pattern, so the settings from `datastream_template` are applied to the new index. | ||
* Designates the new index as the write index and makes the bootstrap index read-only. |
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.
* Designates the new index as the write index and makes the bootstrap index read-only. | |
* Designates the new index as the write index and makes `datastream-000001` read-only. |
|
||
[source,console] | ||
-------------------------------------------------- | ||
GET datastream-*/_ilm/explain | ||
-------------------------------------------------- | ||
// TEST[continued] | ||
|
||
The above request will retrieve {ilm-init} execution information for all our | ||
managed indices. | ||
The response below shows that the bootstrap index is waiting in the `hot` phase's `rollover` action. |
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 response below shows that the bootstrap index is waiting in the `hot` phase's `rollover` action. | |
The response below shows that the `datastream-000001` index is waiting in the `hot` phase's `rollover` action. |
after 90 days. | ||
. <<ilm-gs-create-policy, Create a lifecycle policy>> with the {ilm-init} Put policy API. | ||
. <<ilm-gs-apply-policy, Create an index template>> to apply the policy to each new index. | ||
. <<ilm-gs-bootstrap, Bootstrap an index>> as the initial write index. |
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.
. <<ilm-gs-bootstrap, Bootstrap an index>> as the initial write index. | |
. <<ilm-gs-bootstrap, Create an initial write index>>. |
The intention here is that the rollover alias is also defined on the index. | ||
[float] | ||
[[ilm-gs-bootstrap]] | ||
=== Bootstrap the initial time-series index |
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.
=== Bootstrap the initial time-series index | |
=== Create an initial time-series index |
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.
Left some minor editorial questions/suggestions. Otherwise LGTM.
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Co-Authored-By: James Rodewig <[email protected]>
Thanks for the review @andreidan & @jrodewig! I stuck with the bootstrap terminology, at least for now. (Though since the term now is mostly associated with the framework, it is potentially problematic.) |
* [DOCS] Edit ILM GS tutorial * [DOCS] Incorporated review feedback from @andreidan. * [DOCS] Removed test link & fixed anchor & title. * Update docs/reference/ilm/getting-started-ilm.asciidoc Co-Authored-By: James Rodewig <[email protected]>
* [DOCS] Align with ILM API docs (#48705) * [DOCS] Reconciled with Snapshot/Restore reorg * [DOCS] Split off ILM overview to a separate topic. (#51287) * [DOCS} Split off overview to a separate topic. * [DOCS] Incorporated feedback from @jrodewig. * [DOCS] Edit ILM GS tutorial (#51513) * [DOCS] Edit ILM GS tutorial * [DOCS] Incorporated review feedback from @andreidan. * [DOCS] Removed test link & fixed anchor & title. * Update docs/reference/ilm/getting-started-ilm.asciidoc Co-Authored-By: James Rodewig <[email protected]> * Fixed glossary merge error. Co-authored-by: James Rodewig <[email protected]>
* [DOCS] Align with ILM API docs (elastic#48705) * [DOCS] Reconciled with Snapshot/Restore reorg * [DOCS] Split off ILM overview to a separate topic. (elastic#51287) * [DOCS} Split off overview to a separate topic. * [DOCS] Incorporated feedback from @jrodewig. * [DOCS] Edit ILM GS tutorial (elastic#51513) * [DOCS] Edit ILM GS tutorial * [DOCS] Incorporated review feedback from @andreidan. * [DOCS] Removed test link & fixed anchor & title. * Update docs/reference/ilm/getting-started-ilm.asciidoc Co-Authored-By: James Rodewig <[email protected]> * Fixed glossary merge error. Co-authored-by: James Rodewig <[email protected]>
* [DOCS] Align with ILM API docs (#48705) * [DOCS] Reconciled with Snapshot/Restore reorg * [DOCS] Split off ILM overview to a separate topic. (#51287) * [DOCS} Split off overview to a separate topic. * [DOCS] Incorporated feedback from @jrodewig. * [DOCS] Edit ILM GS tutorial (#51513) * [DOCS] Edit ILM GS tutorial * [DOCS] Incorporated review feedback from @andreidan. * [DOCS] Removed test link & fixed anchor & title. * Update docs/reference/ilm/getting-started-ilm.asciidoc Co-Authored-By: James Rodewig <[email protected]> * Fixed glossary merge error. Co-authored-by: James Rodewig <[email protected]> Co-authored-by: James Rodewig <[email protected]>
No description provided.