-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Index Management] Support data retention on Data Streams tab #165263
[Index Management] Support data retention on Data Streams tab #165263
Conversation
@@ -71,7 +71,6 @@ export const DataStreamTable: React.FunctionComponent<Props> = ({ | |||
render: (health: DataStream['health']) => { | |||
return <DataHealth health={health} />; | |||
}, | |||
width: '100px', |
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.
This was causing some weird spacing issues in the table.
interface TimestampFieldFromEs { | ||
name: string; | ||
} | ||
|
||
type TimestampField = TimestampFieldFromEs; | ||
|
||
interface MetaFromEs { |
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 refactored some of the server-side code to leverage the types from @elastic/elasticsearch
rather than our own custom interfaces
@elasticmachine merge upstream |
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
…t/data_stream_lifecycle
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 a lot for working on data retention, @alisonelizabeth!
Tested locally and the information is displayed as expected, code changes LGTM too 👍
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.
...ication/sections/home/data_stream_list/data_stream_detail_panel/data_stream_detail_panel.tsx
Outdated
Show resolved
Hide resolved
...ication/sections/home/data_stream_list/data_stream_detail_panel/data_stream_detail_panel.tsx
Outdated
Show resolved
Hide resolved
...ication/sections/home/data_stream_list/data_stream_detail_panel/data_stream_detail_panel.tsx
Outdated
Show resolved
Hide resolved
...ication/sections/home/data_stream_list/data_stream_detail_panel/data_stream_detail_panel.tsx
Outdated
Show resolved
Hide resolved
...ication/sections/home/data_stream_list/data_stream_detail_panel/data_stream_detail_panel.tsx
Outdated
Show resolved
Hide resolved
<EuiToolTip | ||
content={i18n.translate('xpack.idxMgmt.dataStreamList.table.dataRetentionColumnTooltip', { | ||
defaultMessage: | ||
'The minimum amount of time the data stream will be stored for. Only applicable for data streams managed by data stream lifecycle.', |
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.
Some suggestions:
The amount of time that a data stream retains its data before it is automatically deleted. Only applies to data streams managed by a data stream lifecycle policy.
The amount of time to keep the data indexed in the data stream. Only applies for data streams managed by a data stream lifecycle.
The amount of time to keep the data stream. Only applies for data streams managed by a data stream lifecycle.
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've learned this value may also not apply to all the data depending on the configuration. From the ES team:
Meaning, they switched from one to the other at some point, so for example: backing indices 1, 2 and 3 are managed by ILM, and backing indices 4 and 5 and any future ones are managed by data stream lifecycle.
Do you think we could work this in as well?
@alisonelizabeth Something that comes up is how well ILM and now DSL enable timely deletion for compliance reasons (GDPR etc). We don't delete the data exactly after 7 days (in the above example) so we should be careful to not give that impression. I wonder if we could improve the first sentence a little as the first time I read it I felt a bit like it implies a guarantee which we know won't be satisfied. It is more like "the minimum amount of time data will be available before it is automatically deleted" or "data will be be kept at least this long before it is automatically deleted" or ? |
Here's a suggestion based on @tylerperk's comment:
|
…t/data_stream_lifecycle
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Public APIs missing exports
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
This PR adds support for viewing the configured data retention value per data stream on the Data Streams tab in Index Management.
On serverless, a data stream can be managed by data stream lifecycle.
On stateful, a data stream can be managed by data stream lifecycle or ILM, or both.
Fixes #165134
Fixes #152720
Fixes #154259
Fixes #165143
Note: Skipping release note for now, however, we will want to add one once the remaining work is complete (meta: #154256)
How to test
Screenshots