eBPF + OTel: Two Layers, One Observability Strategy
Webinar & Live Demo: 9 AM (PST) / 12 PM (EST)
Every observability strategy starts the same way: instrument the services. But that breaks down once you have a few hundred of them, including services you inherited and can't redeploy, languages with alpha-stage instrumentation libraries, and request paths crossing into services another team hasn't touched since 2023
Past a certain size, "complete instrumentation" isn't a goal you're behind on: it's one you'll never reach, and outages happen in exactly those gaps.
This webinar makes the case that neither layer replaces the other:
- eBPF delivers immediate, universal coverage of every process and network path — no code changes, no redeployments, including services nobody got around to instrumenting
- OpenTelemetry delivers the application context eBPF can't see — business identifiers, query shapes, span attributes
The real engineering challenge is deciding where each one earns its overhead.
Live demo: three failure modes where eBPF and OpenTelemetry each answer half the question, and where relying on only one leaves you guessing.
Our Speakers
Anais Dotis | Developer Relations, groundcover
David Flanagan | Founder of Rawkode Academy & K8s expert
















