Details

    • False
    • None
    • False
    • OCPSTRAT-861 - Passive Per-Flow Latency (RTT) Observability
    • NetObserv - Sprint 246, NetObserv - Sprint 247
    • Critical

    Description

      Description of problem:

      Flow RTT values are n/a for flows with protocol TCP and sampling is set to 1

      Steps to Reproduce:

      1. Deploy latest downstream version of the operator
      2. Deploy flowcollector with flowRTT enabled
      3. Go to netflow-traffic page and filter the flows on protocol = TCP
      

      Actual results:

      Flows are observed with FlowRTT value n/a

      Expected results:

      All flows should have flowRtt value!= n/a

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: