eBPF Application Instrumentation for Java: Challenges, Design, and Real...
summary
eBPF daemonset inspects TCP at the kernel with kprobes and uprobe mix and injects a tiny Java agent into running JVMs to extract connection metadata and decrypted buffers so traces and metrics are reconstructed without code or JVM changes. Works on Spring Boot (HTTPS, gRPC), Quarkus (TLS Postgres, Kafka), and JDBC in production; breaks context when apps use separate thread pools or nonstandard JDK behaviors, requires Linux, and sometimes needs protocol tweaks (Kafka v13/v14 handled). TLS cleartext extraction
AI-written summary · about
chapters (9)
- 0:00eBPF Java instrumentation intro
- 1:44Auto instrumentation challenges
- 3:08Oboe architecture
- 7:42Java/eBPF challenges
- 10:10TLS and thread mapping
- 12:38Demos and examples
- 15:24Performance trade-offs
- 17:54OTEL SDK vs Oboe
- 21:57OTEL SDK and Oboe together
related talks
27mJVM & TLS: eBPF's Out-of-Comfort Zone
39mJava Agent vs. eBPF: A Deep Dive into OpenTelemetry Instrumentation Technologies
37meBPF: Revolutionizing Observability and Telemetry for Modern Applications
42mCommunity Driven Breakout Session: eBPF and Auto-Instrumentation
40mPanel Discussion: eBPF: A New Era in Cloud Infrastructure Tools
31meBPF for Observability: The Good, the Bad, and the Ugly
31mZero instrumentation observability with eBPF
37mZero-instrumentation observability based on eBPF