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

Enhance lokiless UX with incompatible filters

    • False
    • None
    • False
    • Hide
      Previously in the Console plugin with disabled Loki, it was very likely to generate a "Can't build query" error due to selecting an incompatible set of filters and aggregations. The tool now makes its best to avoid such error, by automatically disabling incompatible filters, while still making the user know about it.
      Show
      Previously in the Console plugin with disabled Loki, it was very likely to generate a "Can't build query" error due to selecting an incompatible set of filters and aggregations. The tool now makes its best to avoid such error, by automatically disabling incompatible filters, while still making the user know about it.
    • NetObserv - Sprint 263, NetObserv - Sprint 264, NetObserv - Sprint 265

      Description of problem:

      In lokiless mode, it's easy to get in a situation where the desired query is incompatible with the possible prometheus queries. See screenshots & steps.
      We should be able to improve that, for instance by automatically disabling the filters that are incompatible (and throwing a warning, because user needs to know that their query had to be adapted)

      Steps to Reproduce:

      1. Install netobserv with Loki disabled
      2. Go to topology with default filters (it works)
      3. Move scope slider to "Node"
      

      Actual results:

      Error: Can't build query: this request could not be performed with Prometheus metrics, as they are missing some of the required labels. Try using different filters and/or aggregations. For example, try removing these dependencies from your query: K8S_FlowLayer. Alternatively, you may also install and enable Loki
      
      

      Expected results:

      We might run the same query except disabling the unavailable filters, here "layer", "dest. kind" and "source kind". In the UI, those filters should be automatically greyed out to show they have been disabled. A warning popup should tell that the filters were automatically disabled.

              jpinsonn@redhat.com Julien Pinsonneau
              jtakvori Joel Takvorian
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: