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

All DNS graphs get promUnsupported for Loki-less install

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • NetObserv - Sprint 284, NetObserv - Sprint 285
    • None
    • None
    • Hide
      Previously, when Loki is disabled and DNS Tracking is enabled, the console plugin did not show any of the DNS graphs, displaying instead the error "this request could not be performed with Prometheus metrics". This error was displayed for all DNS graphs even though some of them had valid prometheus metrics to work with.
      This error is now displayed strictly for graphs that actually have missing configured metrics. All valid DNS graphs are now correctly displayed.
      Show
      Previously, when Loki is disabled and DNS Tracking is enabled, the console plugin did not show any of the DNS graphs, displaying instead the error "this request could not be performed with Prometheus metrics". This error was displayed for all DNS graphs even though some of them had valid prometheus metrics to work with. This error is now displayed strictly for graphs that actually have missing configured metrics. All valid DNS graphs are now correctly displayed.

      Description of problem:

      In a Loki-less install with DNSTracking option selected, all DNS panels get the error "promUnsupported:this request could not be performed with Prometheus metrics: it requires installing and enabling Loki"
      
      This is expected for DNS Names but I expect to get latency, response codes etc.

      Steps to Reproduce:

      1. Create flow collector without Loki
      2. Set agent privileged and select DNSTracking option
      3. Clear all filters and observe DNS graphs (e.g. DNS latency - see screenshot) 
      

      Actual results:

       

      Expected results:

       

              jtakvori Joel Takvorian
              mifiedle@redhat.com Mike Fiedler
              Mehul Modi Mehul Modi
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: