-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
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
- links to
- mentioned on
(2 mentioned on)