To Production and Beyond: Observability for Modern Spring Aps
summary
Spring Boot 3 apps use Observation API (micrometer 1.10) to auto-create metrics, logs and spans; micrometer-tracing replaces Sleuth for Boot 3 and plugs into Brave vs OpenTelemetry experimental. Demo shows three services (t-service, t-leaf, voter) with Prometheus, Grafana, Loki, Tempo/Zipkin and HikariCP. A missing DB row causes 404/500, fixed by inserting the “English breakfast” record; exemplars link a 180ms high-latency span to a 19ms low one (≈10x) so metrics point back to traces. exemplars and micrometer-tracing enable metrics→trace jump.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker intro
- 1:06What is observability
- 5:19Why observability matters
- 10:12Logging with Spring Boot
- 11:16Metrics with Spring Boot
- 13:02Distributed tracing in Spring
- 16:55Observation API explained
- 23:15Demo application overview
- 25:00Debugging the demo issue
- 26:02Logs to traces with Grafana
- 36:27Fixing the database issue
- 38:56Metrics and latency analysis
- 40:22Traces to metrics with exemplars
- 49:00JVM and application metrics
- 52:08Actuator endpoints overview
- 54:37Spring Boot Admin demo
- 55:21HATEOAS for API discoverability
- 57:49Spring Academy and swag
related talks
55mDemystifying Observability for Spring Applications
58mObservability Beyond the three pillars with Spring
38mObservability 101 with Spring and Micrometer
48mObservability of Your Application
45mObservability for Modern Spring Applications
44mWelcome to the Metrics
47mSpring Boot Observability in Practice: Actuator, Micrometer & OpenTelemetry
51mI Can See Clearly Now: Observability of JVM & Spring Boot 2-3-4 apps