kibana
kibana copied to clipboard
elastic
[Search] [Onboarding] Add metering stats API information to indices GET
Summary
Adds index size and doc count to indices management indices API. This API is available only on ES3, relying on the _metering/stats API to provide this information. The use of the API is scoped only for serverless projects, via a config.
AppEx will roll out the UI changes for the other ES3 project solutions.
Checklist
Delete any items that are not applicable to this PR.
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
- [ ] Documentation was added for features that require explanation or tutorials
- [x] Unit or functional tests were updated or added to match the most common scenarios
- [ ] Flaky Test Runner was used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
- [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
- [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
- [ ] This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
- [ ] This was checked for cross-browser compatibility
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 |
For maintainers
- [ ] This was checked for breaking API changes and was labeled appropriately
Why does Search need this info? Do you have an epic link somewhere?
It'll help having some background about what the changes are needed for.
I found the epic through links referencing this PR. For future reference, we tend to use "fix: xyz-issue" or "relasted-to: abc epic" in Core.
So we try not to explicitly link our private issues in PRs. I agree its better to link them in the PR text when these issues are visible for everyone.
:yellow_heart: Build succeeded, but was flaky
- Buildkite Build
- Commit: dcf5fc96975a2730b99d8d9b1d1dfd457e5e1150
Failed CI Steps
Metrics [docs]
Page load bundle
Size of the bundles that are downloaded on every page load. Target size is below 100kb
| id | before | after | diff |
|---|---|---|---|
indexManagement |
43.5KB | 43.6KB | +57.0B |
History
- :green_heart: Build #230885 succeeded 2d694dc1bb158d8e3e8baf2c04f2928d8875864b
- :broken_heart: Build #230721 failed 76beb3bc49bd0539f6bd2f62d6c7486a79fb6b97
- :broken_heart: Build #230687 failed aa8e4ce492110091323858b4406b7ffaa3279b54
- :broken_heart: Build #230605 failed e48d45f4f45cfc85bb69a10709f9ed517274ac13
- :broken_heart: Build #230514 failed 27fad602f4cb045d605f2eebb031bbef385f5233
To update your PR or re-run it, just comment with:
@elasticmachine merge upstream
