[Index Management][Serverless] Extend Index Management UI to visualize the data usage over the time #192966
Assignees
Labels
enhancement
New value added to drive a business result
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Comments
lukasolson
added
Team:Kibana Management
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
|
Based on several inquiries today, I think we can focus our design work by prioritizing the classes of use cases we want to support with this visualization. We can classify these use cases into three buckets as summarized below. There may be more. I propose that we prioritize bucket 1, "Find Heavy Hitters" because this bucket is most closely related the usage and billing transparency we seek to provide to our serverless customers. Buckets 2 and 3 are indeed useful, but if we treat them as secondary priorities, we may be able to make good design decisions quickly.
|
neptunian
added a commit
that referenced
this issue
Sep 20, 2024
The initial serverless only plugin for viewing data usage and retention in Management. The purpose of this PR is to provide a place for other engineers to work on it, hidden from public use. - Plugin is hidden by default and can be enabled through kibana.yml `xpack.dataUsage.enabled: true` - Currently it will show up in both stateful and serverless (if enabled using config above). When we are ready to make the plugin available we will enable it in config/serverless.yml - Renders a card in Management (serverless) when enabled: <img width="1269" alt="Screenshot 2024-09-19 at 4 14 15 PM" src="https:/user-attachments/assets/705e3866-bc88-436a-8532-2af53167f7b1"> #192965 #192966 --------- Co-authored-by: kibanamachine <[email protected]>
neptunian
added a commit
to neptunian/kibana
that referenced
this issue
Sep 20, 2024
The initial serverless only plugin for viewing data usage and retention in Management. The purpose of this PR is to provide a place for other engineers to work on it, hidden from public use. - Plugin is hidden by default and can be enabled through kibana.yml `xpack.dataUsage.enabled: true` - Currently it will show up in both stateful and serverless (if enabled using config above). When we are ready to make the plugin available we will enable it in config/serverless.yml - Renders a card in Management (serverless) when enabled: <img width="1269" alt="Screenshot 2024-09-19 at 4 14 15 PM" src="https:/user-attachments/assets/705e3866-bc88-436a-8532-2af53167f7b1"> elastic#192965 elastic#192966 --------- Co-authored-by: kibanamachine <[email protected]>
10 tasks
jbudz
pushed a commit
that referenced
this issue
Sep 20, 2024
The initial serverless only plugin for viewing data usage and retention in Management. The purpose of this PR is to provide a place for other engineers to work on it, hidden from public use. - Plugin is hidden by default and can be enabled through kibana.yml `xpack.dataUsage.enabled: true` - Currently it will show up in both stateful and serverless (if enabled using config above). When we are ready to make the plugin available we will enable it in config/serverless.yml - Renders a card in Management (serverless) when enabled: <img width="1269" alt="Screenshot 2024-09-19 at 4 14 15 PM" src="https:/user-attachments/assets/705e3866-bc88-436a-8532-2af53167f7b1"> #192965 #192966 --------- ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https:/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https:/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Multiple Spaces—unexpected behavior in non-default Kibana Space. | Low | High | Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces. | | Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. | High | Low | Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure. | | Code should gracefully handle cases when feature X or plugin Y are disabled. | Medium | High | Unit tests will verify that any feature flag or plugin combination still results in our service operational. | | [See more potential risk examples](https:/elastic/kibana/blob/main/RISK_MATRIX.mdx) | ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) Co-authored-by: kibanamachine <[email protected]>
|
Thanks @MikePaquette I think this would be useful for design as I'm not sure these issues are addressed and the design is still in flux. This design is outdated and I think the new one is still being worked on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Serverless users should be able to analyze how much data they are ingesting (daily/weekly/etc.) and retaining over the selected period of time.
Current Kibana Index Management page shows only the storage size per datastream at the current point of time.
The goal of that issue is to describe the UI scope for the datastreams usage visualization. The Kibana API which will serve it is described as a separate ticket #192965
Extend Data section cards with the new link to the Data Usage page:
The page components:
All the interactive components will call the internal Kibana API here #192965
Mockups: /// TODO
The text was updated successfully, but these errors were encountered: