Architecture
Netra has two workloads: a controller (netrad) that serves the API/UI and holds desired configuration, and a node agent (netra-agent) that owns the eBPF programs and maps on each Linux node.
Optional kernel sensors
Beyond the core cgroup datapath, the agent can run extra sensors. Each one is its own
Access control and export
Everything on this page is off by default and additive: nothing about an existing install
How Netra is tested
Every use case Netra ships has a job in GitHub Actions that runs it for real: a real controller,
Suite placement (PacketWolf)
Netra and PacketWolf are Zyvor suite counterparts covering the same eBPF territory from opposite directions — not a wired pipeline.