Container/netns-aware capture + cgroup attribution #126
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
marcpardo/netring#126
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Roadmap. Forward-looking; possibly breaking on the capture-target API. Correlation-relevant.
Problem
Capture is by interface name only — no network-namespace entry, no container/cgroup tagging. In containerized hosts this misses per-container traffic and can't attribute flows to a workload.
AnyBackendselects an interface; there's nonetns/cgroup dimension.Proposal
Impact
Unlocks container-scoped NDR and feeds ZenSight's host/container entity resolution (correlation epic C9).
Done in
3156e41(0.29.0).NetNshandle (from_name/from_pid/from_path/current, label/inode/try_clone) + scoped-threadrun_in(..)(setns CLONE_NEWNET, no restore — thread exits; fds are netns-independent), andCaptureBuilder::netns(&NetNs)for AF_PACKET capture inside a namespace. Requires CAP_SYS_ADMIN. Monitor-level CaptureTarget/SourceMeta plumbing + cgroup stamping (folds into #130) + AF_XDP-in-netns are documented follow-ups.