-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
Followup onĀ NETOBSERV-1099
INGRESS or EGRESS reporter doesn't provide the same visibility
- mergeFlowReporters needs to be revisited
- metrics default behavior has changed (see
NETOBSERV-1109suggestion)
Connection tracking is not working anymore
- is related to
-
NETOBSERV-1240 DNS flows can be missed with Duplicates "unselected" by default in UI
- Closed
-
NETOBSERV-1244 Default UI filters should show ingress traffic
- Closed
- relates to
-
NETOBSERV-915 Duplicate Conversation events triggered
- Closed
-
NETOBSERV-1109 Reporter node behaves the opposite of what it says (conversations)
- Closed
-
NETOBSERV-646 Allow capturing only ingress/egress traffic
- Closed
-
NETOBSERV-1099 UI: remove reporter option
- Closed
- links to
- mentioned on