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

DNS TCP flows have n/a values

    • False
    • None
    • False
    • OCPSTRAT-965 - DNS tracking improvements
    • NetObserv - Sprint 244
    • Important

      Description of problem:DNS TCP flows show up n/a values for DNS related columns

      Steps to Reproduce:

      1.Deploy latest downstream operator
      2.Create flowcollector with DNSTracking enabled
      3.Deploy pod running DNS queries on TCP by following the steps in https://issues.redhat.com/browse/NETOBSERV-1245 description 
      4.Go to netflow-traffic page and filter on SrcPort 53, DstNamespace <podNS> and protocol TCP
      

      Actual results:

      Some flows have DNS Id, Latency, Response Code fields as n/a

      Expected results:

      All flows should have DNS Id, Latency, Response Code fields should have non-n/a values

      PTAL the screenshot below for reference

            mmahmoud@redhat.com Mohamed Mahmoud
            rhn-support-aramesha Amogh Rameshappa Devapura
            Amogh Rameshappa Devapura Amogh Rameshappa Devapura
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: