Uploaded image for project: 'Observability UI'
  1. Observability UI
  2. OU-309

Tables in dashboards are not merging multiple query responses correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • OpenShift 4.16
    • OpenShift 4.13
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • 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.
    • Sprint 248

      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.

       

              gbernal@redhat.com Gabriel Bernal
              gbernal@redhat.com Gabriel Bernal
              Tai Gao Tai Gao
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: