-
Notifications
You must be signed in to change notification settings - Fork 175
Adding Streams information into the Manage data section #3399
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
Merged
Conversation
This file contains hidden or 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
kilfoyle
reviewed
Oct 9, 2025
kilfoyle
reviewed
Oct 9, 2025
manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
Outdated
Show resolved
Hide resolved
kilfoyle
reviewed
Oct 9, 2025
manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
Outdated
Show resolved
Hide resolved
kilfoyle
reviewed
Oct 9, 2025
manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
Outdated
Show resolved
Hide resolved
kilfoyle
reviewed
Oct 22, 2025
kilfoyle
reviewed
Oct 22, 2025
kilfoyle
reviewed
Oct 22, 2025
kilfoyle
reviewed
Oct 22, 2025
manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
Outdated
Show resolved
Hide resolved
kilfoyle
reviewed
Oct 22, 2025
manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
Outdated
Show resolved
Hide resolved
kilfoyle
reviewed
Oct 22, 2025
...a/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md
Outdated
Show resolved
Hide resolved
kilfoyle
approved these changes
Oct 22, 2025
Contributor
kilfoyle
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.
LGTM! 🚢
These are looking great @yetanothertw! I have a few minor comments about the "Streams" term, but otherwise I think these are "ready to roll". 🎸
yetanothertw
commented
Oct 22, 2025
rhr323
pushed a commit
to rhr323/docs-content
that referenced
this pull request
Oct 27, 2025
Refers to [elastic#274](elastic/docs-content-internal#274) * On the [Data streams](https://www.elastic.co/docs/manage-data/data-store/data-streams) page added an admonition to mention Streams and link to it. * [Tutorial: Update the lifecycle of a data stream](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream) now has a new section Manage data retention in Streams. * [Tutorial: Configure data stream retention](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-data-stream-retention#retention-configuration) has been updated as well. This page may need to be reworked separately in the future as most of its content fits under conceptual type of information rather than tutorial. * [Failure store](https://www.elastic.co/docs/manage-data/data-store/data-streams/failure-store#set-up-failure-store-existing) -- updated the [Set up for existing data streams](https://www.elastic.co/docs/manage-data/data-store/data-streams/failure-store#set-up-failure-store-existing) section to add a tip about performing that in Kibana. * [Modify a data stream](https://www.elastic.co/docs/manage-data/data-store/data-streams/modify-data-stream) -- updated but need to update links to Streams content after Mike's PR is merged. * [View the lifecycle status of an index or data stream](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/policy-view-status) -- updated the Kibana tab to add steps for viewing the lifecycle of a data stream in Streams. * [Manage a data stream](https://www.elastic.co/docs/manage-data/data-store/data-streams/manage-data-stream) -- updated to add a new section about managing data streams in the Streams UI. * [Tutorial: Migrate ILM managed data stream to data stream lifecycle](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle) -- updated to add a note about the ability to switch between ILM and data stream lifecycle in the Streams area in Kibana. --------- Not sure about the impact on these topics: * [Manually apply a lifecycle policy to an index](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/policy-apply) -- I was considering updating this procedure, but I'm not sure anymore because it seems to mostly refer to applying an ILM policy to standalone indices, and not data streams (so the streams feature wouldn't really apply). * [Manage the lifecycle policy for integrations data](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data) -- not sure how this page would be affected. @kilfoyle, would you have any thoughts on this, please?
naemono
pushed a commit
to naemono/docs-content
that referenced
this pull request
Oct 28, 2025
Refers to [elastic#274](elastic/docs-content-internal#274) * On the [Data streams](https://www.elastic.co/docs/manage-data/data-store/data-streams) page added an admonition to mention Streams and link to it. * [Tutorial: Update the lifecycle of a data stream](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream) now has a new section Manage data retention in Streams. * [Tutorial: Configure data stream retention](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-data-stream-retention#retention-configuration) has been updated as well. This page may need to be reworked separately in the future as most of its content fits under conceptual type of information rather than tutorial. * [Failure store](https://www.elastic.co/docs/manage-data/data-store/data-streams/failure-store#set-up-failure-store-existing) -- updated the [Set up for existing data streams](https://www.elastic.co/docs/manage-data/data-store/data-streams/failure-store#set-up-failure-store-existing) section to add a tip about performing that in Kibana. * [Modify a data stream](https://www.elastic.co/docs/manage-data/data-store/data-streams/modify-data-stream) -- updated but need to update links to Streams content after Mike's PR is merged. * [View the lifecycle status of an index or data stream](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/policy-view-status) -- updated the Kibana tab to add steps for viewing the lifecycle of a data stream in Streams. * [Manage a data stream](https://www.elastic.co/docs/manage-data/data-store/data-streams/manage-data-stream) -- updated to add a new section about managing data streams in the Streams UI. * [Tutorial: Migrate ILM managed data stream to data stream lifecycle](https://www.elastic.co/docs/manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle) -- updated to add a note about the ability to switch between ILM and data stream lifecycle in the Streams area in Kibana. --------- Not sure about the impact on these topics: * [Manually apply a lifecycle policy to an index](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/policy-apply) -- I was considering updating this procedure, but I'm not sure anymore because it seems to mostly refer to applying an ILM policy to standalone indices, and not data streams (so the streams feature wouldn't really apply). * [Manage the lifecycle policy for integrations data](https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/manage-lifecycle-integrations-data) -- not sure how this page would be affected. @kilfoyle, would you have any thoughts on this, please?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
Team:Admin
Issues owned by the Admin Docs Team
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.
Refers to #274
On the Data streams page added an admonition to mention Streams and link to it.
Tutorial: Update the lifecycle of a data stream now has a new section Manage data retention in Streams.
Tutorial: Configure data stream retention has been updated as well. This page may need to be reworked separately in the future as most of its content fits under conceptual type of information rather than tutorial.
Failure store -- updated the Set up for existing data streams section to add a tip about performing that in Kibana.
Modify a data stream -- updated but need to update links to Streams content after Mike's PR is merged.
View the lifecycle status of an index or data stream -- updated the Kibana tab to add steps for viewing the lifecycle of a data stream in Streams.
Manage a data stream -- updated to add a new section about managing data streams in the Streams UI.
Tutorial: Migrate ILM managed data stream to data stream lifecycle -- updated to add a note about the ability to switch between ILM and data stream lifecycle in the Streams area in Kibana.
Not sure about the impact on these topics:
Manually apply a lifecycle policy to an index -- I was considering updating this procedure, but I'm not sure anymore because it seems to mostly refer to applying an ILM policy to standalone indices, and not data streams (so the streams feature wouldn't really apply).
Manage the lifecycle policy for integrations data -- not sure how this page would be affected. @kilfoyle, would you have any thoughts on this, please?