Decorate the flows with extra metadata fields that are not directly fetched by eBPF or by any previous pipeline stage (DNS, Kubernetes...): - The interface name (corresponding to the interface index in the flow).

DeduperProvider receives flows and filters these belonging to duplicate interfaces.

ProtocolFilterProvider allows selecting which protocols are going to be instrumented.

MapTracer accesses a mapped source of flows (the eBPF PerCPU HashMap), deserializes it into a flow Record structure, and performs the accumulation of each perCPU-record into a single flow.

ReverseDNS is currently experimental.

RingBufTracer receives single-packet flows via ringbuffer (usually, these that couldn't be added in the eBPF kernel space due to the map being full or busy) and submits them to the userspace Aggregator map.