Epic Goal

The goal of this epic is to enable flow / packet capture in network observability stack.

Pcap brainstorming doc

Netobserv CLI

The filtering on captured flows should be either piloted from console plugin or CRD.

It should include:

• The target pod(s) identification (pod name, or controller name, or pod labels)
• Some optional filters:
  • Flow direction: ingress / egress / both
  • Peer name / type / ip / port
• Time limit and/or packet count limit (capture first N packets)
• Sampling

For now the agents restarts on changes. We should find a way to avoid disrupting the capture when filtering is updated.

Why is this important?

-...

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

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