Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Docs QE Status:
NEW
QE Status:
NEW
Release Note Text:

Hide
Before the fix, dashboard tables calculated metrics by considering only unique values for the first label, leading to tables showing just a single row. With the fix applied, metrics now account for unique values across all labels, ensuring that all possible rows are displayed.

Show
Before the fix, dashboard tables calculated metrics by considering only unique values for the first label, leading to tables showing just a single row. With the fix applied, metrics now account for unique values across all labels, ensuring that all possible rows are displayed.
Intelligence Requested:
Market:

A table in a dashboard relies on the order of the metric labels to merge results

How to Reproduce:

Create a dashboard with a table including this query:

label_replace(sort_desc(sum(sum_over_time(ALERTS{alertstate="firing"}[24h])) by ( alertstate, alertname)), "aaa", "$1", "alertstate", "(.+)")

A single row will be displayed as the query is simulating that the first label `aaa` has a single value.

Expected result:

The table should not rely on a single metric label to merge results but consider all the labels so the expected rows are displayed.

clones

OU-309 Tables in dashboards are not merging multiple query responses correctly

links to