-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
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
- is related to
-
NETOBSERV-917 Connection tracking usability feedback
- To Do
-
NETOBSERV-1109 Reporter node behaves the opposite of what it says (conversations)
- Closed
- links to