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

Conversation tracking improvements

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Operator
    • Proactive Architecture
    • 3
    • False
    • None
    • False

      Followup on https://issues.redhat.com/browse/NETOBSERV-915

      We could optimize the way conversation tracking works in multiple ways:

      • changing the order of the stages to enrich and reinterpret direction first and keep the enriched fields in conversation tracking
      • tweak default values and move the ones the customer may not change in debug section
      • manage values per protocols as shown in https://github.com/netobserv/flowlogs-pipeline/pull/357 
      • think about aggregating interfaces and directions in records

      This task aim to define what to do and implement it

      See https://github.com/netobserv/flowlogs-pipeline/pull/430#issuecomment-1576429302 & https://github.com/netobserv/network-observability-operator/pull/313#discussion_r1214272223 

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

              Created:
              Updated: