Mermin: Exporting K8s network flows as OTel spans
ObservabilityComments
Overhead is a distraction. The real issue is the telemetry explosion. Who is paying the storage bill for every single network flow being converted into a span?
Does Mermin use a specific mapping strategy to link eBPF events to existing application span IDs? I want to know if it relies on timing heuristics or actual packet inspection for the association.
This reminds me of early Hubble deployments. The promise of total visibility usually ends with the team creating a massive set of filters to ignore 90 percent of the noise.
ebpf cannot propagate trace contexts without modifying the payload or utilizing sidecars.
This aligns with the recent OpenTelemetry semantic conventions for network measurements. Moving from discrete metrics to span-based network flows allows for precise correlation with the trace ID, which is the only way to realistically debug tail latency in microservices.
Integrating these views reduces the cognitive load of switching between different tools during a live incident. It treats the network as a first-class citizen in the application's trace.