-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
NetObserv - Sprint 228, NetObserv - Sprint 229, NetObserv - Sprint 230, NetObserv - Sprint 231, NetObserv - Sprint 232, NetObserv - Sprint 233, NetObserv - Sprint 234, NetObserv - Sprint 235, NetObserv - Sprint 236
-
Critical
By default, if a pod makes an external request such as a web request, only the request flow is in the flow table. The response flow is missing. See 01-dest.png, 1st row.
In order to see the request and response, in Query Options, "Both" must be selected. However, this doubles the number of internal flows because the source node and destination node are reporting the same flow.
A possible solution is to get all flows and deduplicate. Ideally, information on what nodes the flows have traversed should be preserved. If done right, the Reporter node option can be removed.
I consider this a bug because users will be surprised that flows are missing, and even if they know there is a "Both" option, it is not practical to use because it shows duplicated flows for all internal traffic.
- depends on
-
NETOBSERV-759 Add a way to identify agent in flows
- Closed
- relates to
-
NETOBSERV-915 Duplicate Conversation events triggered
- Closed
- links to