Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1719

Lokiless console: improve UX for wrong combination of filters

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Console Plugin
    • None
    • Improvement
    • False
    • None
    • False

      When console plugin uses only Prometheus, some queries cannot be performed because the combination of filters/aggregations/value field is invalid.

      Examples:

      • Filtering on a namespace, and setting Topology scope to Nodes
      • Filtering on Packet drop cause, and having value field to Bytes (instead of Dropped bytes)

      Currently, an error is returned, telling that this query requires Loki. Which is true, but we could also do more:

      • We could display a warning icon next to scopes that wouldn't work for the current set of filters.. and/or the other way around, same icon next to filters that wouldn't work for the current selected scope.
      • We should try improving the error message by saying more precisely which set of filters/labels is invalid
      • For drop cause/state filters in particular, we could switch automatically to use Dropped bytes/Packets as the value field, transparently. doing so via https://github.com/netobserv/network-observability-console-plugin/pull/549
      • In Overview, when some queries fail but not all, do not make the whole page showing an error. Instead, display what we can, and show the error contextual to the graph where it failed

              Unassigned Unassigned
              jtakvori Joel Takvorian
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: