[Metrics][Discover] Build Metrics Grid chart from METRICS_INFO response by kpatticha · Pull Request #257206 · elastic/kibana

kpatticha · 2026-03-11T14:24:46Z

Summary

Changes how the Metrics experience grid is built and rendered: we no longer use Field Caps and now rely on the ES|QL METRICS_INFO pipeline as the single source of metris grid. Data is fetched, parsed, and typed in kbn-unified-chart-section-viewer.

Major changes

Data source: Grid is driven by METRICS_INFO instead of Field Caps. Fetch via useFetchMetricsData (ES|QL + | METRICS_INFO), parse with parseMetricsResponse; grid and toolbar consume metricItems and allDimensions from this hook.
Filtering: When multiple dimension names are selected, a WHERE dimension filter (e.g. field IS NOT NULL) is applied in buildMetricsInfoQuery before METRICS_INFO.
Types: ParsedMetricItem and ParsedMetricsResult describe the flow; grid, chart layers, flyout, and content use this shape (metricName, dataStream, fieldTypes, metricTypes, units, dimensionFields). Public API exports ParsedMetricItem, ParsedMetricsResult, MetricsInfoResponse, MetricsESQLResponseObject, Dimension, MetricUnit, UnifiedMetricsGridProps.
Naming: Parser returns metricItems / allDimensions; hook returns metricItems;
Search/filter: Client-side only via useMetricFieldsFilter and filteredMetricItems (no Field Caps).
Tests: Updated and added mocks for useFetchMetricsData, useMetricFieldsFilter, and related hooks.

Behavior

SORT only: FROM x | SORT timestamp DESC → FROM x | METRICS_INFO (SORT removed).
LIMIT only: FROM x | LIMIT 10 → FROM x | METRICS_INFO | LIMIT 10.
SORT + LIMIT: FROM x | SORT ts | LIMIT 100 → FROM x | METRICS_INFO | LIMIT 100.
WHERE + SORT + LIMIT: Existing WHERE is kept; SORT is removed; LIMIT is re-appended after METRICS_INFO.

Not addressed

Multi-value in flyout: Handling/display of multi-value fields in the metric insights flyout will be done in a separate ticket.
Dimension/Naming refactor: Simplification of dimension handling (e.g. Dimension[] vs string[], selector, state) is out of scope here and will be done in a separate change. Keep the Dimension[] type

Screen.Recording.2026-03-13.at.4.32.14.PM.mov

How to test

use https://github.com/simianhacker/simian-forge
run npm run build
./forge --dataset histograms --count 3 --interval 10s
go to discover

- Introduced `fetchMetricsInfo` and `parseMetricsInfoResponse` functions to handle fetching and parsing of metrics information. - Updated existing components to utilize the new metrics info structure, including adjustments to metric fields and dimensions. - Added utility functions for normalizing and appending metrics info queries. - Implemented tests for new functionalities to ensure reliability and correctness. This update improves the overall metrics experience by providing a more structured approach to handling metrics data.

kpatticha · 2026-03-11T14:25:41Z

@@ -1,67 +0,0 @@
-/*


Note: I just moved this file

kpatticha · 2026-03-11T14:40:46Z

@@ -41,14 +41,17 @@ export const OverviewTab = ({ metric, description }: OverviewTabProps) => {
  const [itemsPerPage, setItemsPerPage] = useState(DEFAULT_PAGINATION_SIZE);
  const [containerRef, setContainerRef] = useState<HTMLDivElement | null>(null);

-  const unitLabel = useMemo(() => getUnitLabel({ unit: metric.unit }), [metric.unit]);
+  const unitLabel = useMemo(


The multi value for all field in the flyout it will be handled in a follow up ticket: #253718

kpatticha · 2026-03-11T14:53:59Z

/oblt-deploy

lucaslopezf

thanks for sharing! Overall, I agree with the approach. I’ll let you mark the PR as ready for review before adding the comments, and I’ll keep an eye on it so I can provide quick feedback.

…edMetricItem

justinkambic

Great work! I did an initial review. I commented on a couple type errors but tried to stick more toward things I think would be useful as initial feedback.

One thing I noticed in practical testing is if I click a breakdown field from Discover's fields list, basically nothing happens. Are we considering how this will interact with fields that don't display in the Dimensions dropdown list, but do display in Discover's fields list?

…trics_expr

…na into metrics_info_metrics_expr

lucaslopezf

Nice work! I left some comments. I haven’t finished the review yet, so I’ll continue, but I wanted to give you some initial feedback.

lucaslopezf

I left a few more comments. I didn’t review the tests or related things yet, I’ll let you finish that part first before making any noise and then I'll do a second round of review. I’ll also trigger the E2E tests to save some CI time

lucaslopezf · 2026-03-13T11:55:05Z

/flaky scoutConfig:src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts:1

kibanamachine · 2026-03-13T11:55:23Z

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#11087

src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts x1

kibanamachine · 2026-03-13T12:51:50Z

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#11087

[✅] src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts: 1/1 tests passed.

see run history

lucaslopezf

Nice!! We’re really close! Regardless of the comments (nits), while looking at the E2E tests I realized that tests related to queries like TS metrics-* | SORT @timestamp DESC are not working. I tested it locally and the same thing happens

kpatticha · 2026-03-16T15:00:07Z

Nice!! We’re really close! Regardless of the comments (nits), while looking at the E2E tests I realized that tests related to queries like TS metrics-* | SORT @timestamp DESC are not working. I tested it locally and the same thing happens

Yes, these test are gold.

It turns out that we cannot use METRICS_INFO after limit and sort. https://github.com/elastic/elasticsearch/blob/44207cb2e522baa392ba84d18ba0ac83ca1da24b/x-pack/plugin/esql/src/test/java/org/elasticsearch/xpack/esql/analysis/VerifierTests.java#L3762-L3768 .

I'm fixing the limit but for sort I will remove it for now and create a seperate ticket cause I need product input on this

kpatticha · 2026-03-16T16:26:37Z

/flaky scoutConfig:src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts:30

kpatticha · 2026-03-16T16:26:53Z

/oblt-deploy

kibanamachine · 2026-03-16T16:26:57Z

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#11103

src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts x30

kibanamachine · 2026-03-16T17:49:18Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#11103

[❌] src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts: 25/30 tests passed.

see run history

elasticmachine · 2026-03-16T17:58:28Z

💚 Build Succeeded

Buildkite Build
Commit: 02a1603

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`discover`	1988	1989	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/unified-chart-section-viewer`	3	31	+28

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`discover`	1.6MB	1.6MB	-1.6KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`@kbn/unified-chart-section-viewer`	3	2	-1
`@kbn/unified-histogram`	11	12	+1
total			-0

Unknown metric groups

API count

id	before	after	diff
`@kbn/unified-chart-section-viewer`	5	35	+30

History

💚 Build #409824 succeeded f633fc0
💔 Build #409772 failed 51d0d38
💔 Build #409639 failed c92d3be
💔 Build #409229 failed 75fe1a7
💔 Build #409209 failed a2df496
💔 Build #409194 failed c6351e8

elasticmachine · 2026-03-17T09:15:18Z

Pinging @elastic/obs-exploration-team (Team:obs-exploration)

lucaslopezf · 2026-03-17T09:36:29Z

/flaky scoutConfig:src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts:30

kibanamachine · 2026-03-17T09:36:45Z

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#11111

src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts x30

lucaslopezf

Amazing work 🚀 !! Everything looks good to me! Let’s just wait for the flaky tool before merging, and “fix” any flaky tests if we find any

kibanamachine · 2026-03-17T10:59:25Z

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#11111

[❌] src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts: 26/30 tests passed.

see run history

kpatticha · 2026-03-17T11:38:23Z

The flaky tests failed again, 26/30 but I'm going to merge this PR and fix this in a follow up

…metrics experience tests (#258274) Closes: #258227 ## Summary The test used a relative time range (`Last 30 days`) that doesn't overlap with the test data (Jan 2025), so the `METRICS_INFO` query returns empty results and the grid disappears. Replaced with an absolute range (`Jan 1 – Jun 30, 2025`) that covers the test data while still validating grid persistence across time range changes. Surfaced by #257206, which switched to time-range-aware `METRICS_INFO` queries. The test had a latent bug (relative date with no data) that was previously masked by the old field-metadata-based approach. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

…metrics experience tests (elastic#258274) Closes: elastic#258227 ## Summary The test used a relative time range (`Last 30 days`) that doesn't overlap with the test data (Jan 2025), so the `METRICS_INFO` query returns empty results and the grid disappears. Replaced with an absolute range (`Jan 1 – Jun 30, 2025`) that covers the test data while still validating grid persistence across time range changes. Surfaced by elastic#257206, which switched to time-range-aware `METRICS_INFO` queries. The test had a latent bug (relative date with no data) that was previously masked by the old field-metadata-based approach. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

…se (elastic#257206) close elastic#253717 close elastic#253435 ## Summary Changes how the Metrics experience grid is built and rendered: we no longer use Field Caps and now rely on the ES|QL `METRICS_INFO` pipeline as the single source of metris grid. Data is fetched, parsed, and typed in `kbn-unified-chart-section-viewer`. ## Major changes - **Data source**: Grid is driven by METRICS_INFO instead of Field Caps. Fetch via `useFetchMetricsData` (ES|QL + `| METRICS_INFO`), parse with `parseMetricsResponse`; grid and toolbar consume `metricItems` and `allDimensions` from this hook. - **Filtering**: When multiple dimension names are selected, a WHERE dimension filter (e.g. `field IS NOT NULL`) is applied in `buildMetricsInfoQuery` before `METRICS_INFO`. - **Types**: `ParsedMetricItem` and `ParsedMetricsResult` describe the flow; grid, chart layers, flyout, and content use this shape (`metricName`, `dataStream`, `fieldTypes`, `metricTypes`, `units`, `dimensionFields`). Public API exports `ParsedMetricItem`, `ParsedMetricsResult`, `MetricsInfoResponse`, `MetricsESQLResponseObject`, `Dimension`, `MetricUnit`, `UnifiedMetricsGridProps`. - **Naming**: Parser returns `metricItems` / `allDimensions`; hook returns `metricItems`; - **Search/filter**: Client-side only via `useMetricFieldsFilter` and `filteredMetricItems` (no Field Caps). - **Tests**: Updated and added mocks for `useFetchMetricsData`, `useMetricFieldsFilter`, and related hooks. ## Behavior - **SORT only:** `FROM x | SORT timestamp DESC` → `FROM x | METRICS_INFO` (SORT removed). - **LIMIT only:** `FROM x | LIMIT 10` → `FROM x | METRICS_INFO | LIMIT 10`. - **SORT + LIMIT:** `FROM x | SORT ts | LIMIT 100` → `FROM x | METRICS_INFO | LIMIT 100`. - **WHERE + SORT + LIMIT:** Existing WHERE is kept; SORT is removed; LIMIT is re-appended after METRICS_INFO. ## Not addressed - **Multi-value in flyout**: Handling/display of multi-value fields in the metric insights flyout will be done in a separate ticket. - ~**Dimension/Naming refactor**: Simplification of dimension handling (e.g. `Dimension[]` vs `string[]`, selector, state) is out of scope here and will be done in a separate change.~ Keep the Dimension[] type https://github.com/user-attachments/assets/0d865735-ac21-418e-9fb0-16078dfc52f2 ## How to test 1. use https://github.com/simianhacker/simian-forge 2. run `npm run build` 3. `./forge --dataset histograms --count 3 --interval 10s` 4. go to discover --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Lucas Francisco López <lucaslopezf@gmail.com>

…metrics experience tests (elastic#258274) Closes: elastic#258227 ## Summary The test used a relative time range (`Last 30 days`) that doesn't overlap with the test data (Jan 2025), so the `METRICS_INFO` query returns empty results and the grid disappears. Replaced with an absolute range (`Jan 1 – Jun 30, 2025`) that covers the test data while still validating grid persistence across time range changes. Surfaced by elastic#257206, which switched to time-range-aware `METRICS_INFO` queries. The test had a latent bug (relative date with no data) that was previously masked by the old field-metadata-based approach. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

…se (elastic#257206) close elastic#253717 close elastic#253435 ## Summary Changes how the Metrics experience grid is built and rendered: we no longer use Field Caps and now rely on the ES|QL `METRICS_INFO` pipeline as the single source of metris grid. Data is fetched, parsed, and typed in `kbn-unified-chart-section-viewer`. ## Major changes - **Data source**: Grid is driven by METRICS_INFO instead of Field Caps. Fetch via `useFetchMetricsData` (ES|QL + `| METRICS_INFO`), parse with `parseMetricsResponse`; grid and toolbar consume `metricItems` and `allDimensions` from this hook. - **Filtering**: When multiple dimension names are selected, a WHERE dimension filter (e.g. `field IS NOT NULL`) is applied in `buildMetricsInfoQuery` before `METRICS_INFO`. - **Types**: `ParsedMetricItem` and `ParsedMetricsResult` describe the flow; grid, chart layers, flyout, and content use this shape (`metricName`, `dataStream`, `fieldTypes`, `metricTypes`, `units`, `dimensionFields`). Public API exports `ParsedMetricItem`, `ParsedMetricsResult`, `MetricsInfoResponse`, `MetricsESQLResponseObject`, `Dimension`, `MetricUnit`, `UnifiedMetricsGridProps`. - **Naming**: Parser returns `metricItems` / `allDimensions`; hook returns `metricItems`; - **Search/filter**: Client-side only via `useMetricFieldsFilter` and `filteredMetricItems` (no Field Caps). - **Tests**: Updated and added mocks for `useFetchMetricsData`, `useMetricFieldsFilter`, and related hooks. ## Behavior - **SORT only:** `FROM x | SORT timestamp DESC` → `FROM x | METRICS_INFO` (SORT removed). - **LIMIT only:** `FROM x | LIMIT 10` → `FROM x | METRICS_INFO | LIMIT 10`. - **SORT + LIMIT:** `FROM x | SORT ts | LIMIT 100` → `FROM x | METRICS_INFO | LIMIT 100`. - **WHERE + SORT + LIMIT:** Existing WHERE is kept; SORT is removed; LIMIT is re-appended after METRICS_INFO. ## Not addressed - **Multi-value in flyout**: Handling/display of multi-value fields in the metric insights flyout will be done in a separate ticket. - ~**Dimension/Naming refactor**: Simplification of dimension handling (e.g. `Dimension[]` vs `string[]`, selector, state) is out of scope here and will be done in a separate change.~ Keep the Dimension[] type https://github.com/user-attachments/assets/0d865735-ac21-418e-9fb0-16078dfc52f2 ## How to test 1. use https://github.com/simianhacker/simian-forge 2. run `npm run build` 3. `./forge --dataset histograms --count 3 --interval 10s` 4. go to discover --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Lucas Francisco López <lucaslopezf@gmail.com>

…metrics experience tests (elastic#258274) Closes: elastic#258227 ## Summary The test used a relative time range (`Last 30 days`) that doesn't overlap with the test data (Jan 2025), so the `METRICS_INFO` query returns empty results and the grid disappears. Replaced with an absolute range (`Jan 1 – Jun 30, 2025`) that covers the test data while still validating grid persistence across time range changes. Surfaced by elastic#257206, which switched to time-range-aware `METRICS_INFO` queries. The test had a latent bug (relative date with no data) that was previously masked by the old field-metadata-based approach. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

kpatticha added 2 commits March 10, 2026 15:35

Parse metrics info data

b45649b

kpatticha commented Mar 11, 2026

View reviewed changes

Clean up and fixed

20f0b0b

kpatticha commented Mar 11, 2026

View reviewed changes

lucaslopezf reviewed Mar 11, 2026

View reviewed changes

miguel-sanchez-elastic mentioned this pull request Mar 12, 2026

[GA] Metrics in Discover - Use METRICS_INFO to retrieve the metrics catalog #248321

Closed

45 tasks

kpatticha added 5 commits March 12, 2026 16:39

Refactor the fetching metrics info

60fae59

Updated various components and hooks to replace MetricField with Pars…

5aa7ace

…edMetricItem

Render only the supported metric types

a19d3ee

Remove field caps functionality

e517f99

Support filtering

c6351e8

kpatticha marked this pull request as ready for review March 12, 2026 16:58

kpatticha requested a review from a team as a code owner March 12, 2026 16:58

kibanamachine added 2 commits March 12, 2026 17:06

Changes from node scripts/lint_ts_projects --fix

712c7a8

Changes from node scripts/regenerate_moon_projects.js --update

a2df496

elastic-vault-github-plugin-prod Bot requested a review from a team as a code owner March 12, 2026 17:19

Changes from node scripts/eslint_all_files --no-cache --fix

75fe1a7

justinkambic reviewed Mar 12, 2026

View reviewed changes

kpatticha added 3 commits March 13, 2026 12:23

Merge branch 'main' of github.com:elastic/kibana into metrics_info_me…

e9d4290

…trics_expr

Clean up and fix types

d0c8a5e

Merge branch 'metrics_info_metrics_expr' of github.com:kpatticha/kiba…

c92d3be

…na into metrics_info_metrics_expr

lucaslopezf reviewed Mar 13, 2026

View reviewed changes

lucaslopezf mentioned this pull request Mar 13, 2026

[Metrics][Discover] Monitoring for METRICS_INFO fetching #256439

Merged

Fix test

d907ba9

kpatticha requested review from justinkambic and lucaslopezf March 16, 2026 11:11

lucaslopezf reviewed Mar 16, 2026

View reviewed changes

kpatticha added 2 commits March 16, 2026 17:57

Fix METRICS_INFO with LIMIT and SORT

5e9b8db

Address PR comments

02a1603

jughosta mentioned this pull request Mar 16, 2026

[Discover] Introduce an enriched data view clone for ES|QL mode and skip data view fields fetching #256714

Draft

10 tasks

kpatticha requested a review from lucaslopezf March 16, 2026 16:24

kpatticha mentioned this pull request Mar 16, 2026

[Metrics][Discover] Handle SORT validation when using METRICS_INFO #257964

Open

lucaslopezf added the Team:obs-exploration Observability Exploration team label Mar 17, 2026

lucaslopezf approved these changes Mar 17, 2026

View reviewed changes

kpatticha merged commit 71abf0f into elastic:main Mar 17, 2026
20 checks passed

kibanamachine added the v9.4.0 label Mar 17, 2026

lucaslopezf mentioned this pull request Mar 18, 2026

[Discover][Metrics]: E2E - Use absolute range instead of relative in metrics experience tests #258274

Merged

10 tasks

Conversation

kpatticha commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Major changes

Behavior

Not addressed

How to test

Uh oh!

kpatticha Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

kpatticha Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kpatticha commented Mar 11, 2026

Uh oh!

lucaslopezf left a comment

Choose a reason for hiding this comment

Uh oh!

justinkambic left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lucaslopezf left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lucaslopezf left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

lucaslopezf commented Mar 13, 2026

Uh oh!

kibanamachine commented Mar 13, 2026

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#11087

Uh oh!

kibanamachine commented Mar 13, 2026

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#11087

Uh oh!

lucaslopezf left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kpatticha commented Mar 16, 2026

Uh oh!

kpatticha commented Mar 16, 2026

Uh oh!

kpatticha commented Mar 16, 2026

Uh oh!

kibanamachine commented Mar 16, 2026

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#11103

Uh oh!

kibanamachine commented Mar 16, 2026

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#11103

Uh oh!

elasticmachine commented Mar 16, 2026

💚 Build Succeeded

kpatticha commented Mar 11, 2026 •

edited

Loading

kpatticha Mar 11, 2026 •

edited

Loading

lucaslopezf left a comment •

edited

Loading