Instrument Your Native Spring Boot and Quarkus Applications with OpenTelemetry
summary
Shows building native Spring Boot and Quarkus apps as GraalVM native images using Docker multi-stage builds, instrumenting them with OpenTelemetry Java libraries and a custom Azure Application Insights exporter (since OTLP isn’t yet supported on Azure). Demonstrates live that startup times fall to ~500 ms for Spring native and ~100 ms for Quarkus native, and that end-to-end traces capture HTTP spans and Postgres queries across services; recommends sampling at 1–10% and provides code and demos on GitHub.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:56What is OpenTelemetry
- 7:33GraalVM native images
- 10:51Native instrumentation constraints
- 11:53Spring Boot native demo
- 15:30Add OpenTelemetry to Spring Boot
- 19:50Spring Boot telemetry results
- 20:13Quarkus native instrumentation
- 22:40Quarkus native demo
- 24:56Tracing service calls
- 27:44Distributed trace visualization
- 28:06Spring Boot outlook
- 29:29Quarkus outlook
- 31:22Summary and benefits
- 32:34Q&A
related talks
42mDistributed Tracing Integration with OpenTelemetry and Knative
26mEmpowering Quarkus Applications with AI and OpenTelemetry on Kubernetes
59mQuarkus for Spring Developers
51mKubernetes Native Spring apps on Quarkus
08mOpenTelemetry and Quarkus
40mDistributed Tracing Integration with OpenTelemetry and Knative
44mQuarkus: Supersonic Subatomic Java
54mQuarkus: Java development turned into delight
