ElastiFlow for DevOps
Network Context for Your OTel Pipelne
For DevOps teams, the network is a black box, forcing SREs and engineers to wait on NetOps for answers when performance issues arise. ElastiFlow breaks down these silos by bringing network flow traces directly into the OpenTelemetry (OTel) tools you already use, providing the high-fidelity data needed to prove it’s not the app and get back to shipping code.
Why Should DevOps Collect Network Data?
Observability is split. APM sees the application. NPM sees the network. When performance issues arise, the blame game begins and MTTR suffers.
ElastiFlow enables teams to instantly answer "Is it the app or the network?" by adding flow traces to your OTel workflows. ElastiFlow's app-flow correlation provides the necessary context to understand how the network is impacting your app performance and answer. This allows teams to answer questions such as "How much latency was caused by the network vs the application?" and "Are my Kubernetes network policies applied correctly?"
How Can DevOps Collect Network Data?
You shouldn't have to rewrite your application to understand the network. ElastiFlow enables you to auto-instrument your network traffic to provide the context you need without manual effort. Our OpenTelemetry native, open-source eBPF agent, Mermin, is the perfect place to start collecting network data. It runs as a DeamonSet on your Kubernetes cluster or VM host and starts collecting data as soon as it is installed. No code or configuration changes required.
Auto-Instrument Kubernetes Network Traffic with Mermin
Close the Kubernetes observability gap by adding network flow traces to your OTel workflows.
Mermin is an open-source solution that uses eBPF to capture network traffic and export it as Flow Traces via the OpenTelemetry Protocol. Deploy once per node and gain deep visibility into your cluster's network communications — no application changes required.