[Metrics][Discover] Filter by value: Dropdown list is inconsistent with charts data

[miguel-sanchez-elastic]

Description

There is a data inconsistency between the metric charts and the "Filter by value" dropdown. Some values that are clearly visible as series in the charts are missing from the filter list.

This is not related to any display limit (like the 20-item cap), as this behavior is observed even when the total number of unique values is very small (e.g., only two values are visible, but one may be missing from the filter).

Note: in this case it is the same metric name coming from two different indexes but it might not be the only case

This suggests the query populating the filter list is not correctly or completely reflecting the data being displayed in the charts for the current context.

Acceptance criteria

• GIVEN a user is viewing metrics broken down by a dimension AND a chart visibly shows data for a each value
  • WHEN the user opens the "Filter by value" dropdown
  • THEN each specific value MUST be present in the list of options to select
• The change is included in the next 9.2.x version

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[crespocarlos]

The reason why this happens is that attributes.cpu has different types on different indices. This could happen to any field.

".ds-metrics-generic.otel-default-2025.07.25-000052": {
    "mappings": {
      "attributes.cpu": {
        "full_name": "attributes.cpu",
        "mapping": {
          "cpu": {
            "type": "long",
            "time_series_dimension": true
          }
        }
      }
    }
  },

".ds-metrics-hostmetricsreceiver.otel-default-2025.07.11-000068": {
    "mappings": {
      "attributes.cpu": {
        "full_name": "attributes.cpu",
        "mapping": {
          "cpu": {
            "type": "keyword",
            "ignore_above": 1024,
            "time_series_dimension": true
          }
        }
      }
    }
  },

We'll need to revisit the query that fetches the values

[miguel-sanchez-elastic]

Hi @crespocarlos , but why it would not show in the dropdown? is it because we try to create a list of values of type X and the ones from type Y do not enter in that list? In other words, do we need to make a list of fields from any type?

Or are there other product implications that I'd need to understand?

[crespocarlos]

Hi @crespocarlos , but why it would not show in the dropdown? is it because we try to create a list of values of type X and the ones from type Y do not enter in that list? In other words, do we need to make a list of fields from any type?

Or are there other product implications that I'd need to understand?

Elasticseach fails to aggregate on fields that have different types. We'll need to change the query to be able to return all possible values