-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
netobserv-1.7, netobserv-1.7-candidate
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
NetObserv - Sprint 261, NetObserv - Sprint 262, NetObserv - Sprint 263, NetObserv - Sprint 264, NetObserv - Sprint 265, NetObserv - Sprint 266, NetObserv - Sprint 267, NetObserv - Sprint 268, NetObserv - Sprint 269, NetObserv - Sprint 270, NetObserv - Sprint 271, NetObserv - Sprint 272, NetObserv - Sprint 273, NetObserv - Sprint 274, NetObserv - Sprint 275, NetObserv - Sprint 276
-
None
-
None
-
None
Description of problem:
<br> tags showing in the Flow Collector config dialog in Operator Hub: Agent feature, can be one of:<br> - `PacketDrop`, to track packet drops.<br> - `DNSTracking`, to track specific information on DNS traffic.<br> - `FlowRTT`, to track TCP latency.<br> - `NetworkEvents`, to track Network events.<br>
Steps to Reproduce:
1. Create a Flow Collector in Operator Hub 2. Expand eBPF Agent configuration -> Features
Actual results:
Agent feature, can be one of:<br> - `PacketDrop`, to track packet drops.<br> - `DNSTracking`, to track specific information on DNS traffic.<br> - `FlowRTT`, to track TCP latency.<br> - `NetworkEvents`, to track Network events.<br>
Expected results:
- relates to
-
NETOBSERV-1943 Implement configuration view
-
- Closed
-
- links to
