Is your JVM app flying blind? Unmask hidden issues with Observability superpowers!
summary
A runnable microservice demo is instrumented with micrometer observation (no agent), Prometheus, Grafana, Loki, OpenTelemetry, Eureka, RabbitMQ, MongoDB and Postgres; traffic is ~5 req/s, a quota enforces max=2 so throughput drops 5→2, and a missing "English Breakfast" row triggers 500s. Metrics use exemplars jump to spans to pivot into distributed traces, traces point to a 153ms DB call (normal 15ms) caused by toxiproxy latency, and adding a MongoDB index plus removing the proxy restores performance.
AI-written summary · about
chapters (21)
- 0:00Introduction to observability
- 1:24Brewing tea system demo
- 3:12UI and demo failures
- 6:48Debugging server errors
- 8:13Native observability in Spring Boot
- 9:18Micrometer observation explained
- 13:59Testing throughput and errors
- 15:44Distributed tracing basics
- 17:12Fixing missing tea leaf
- 20:17Correlating metrics and traces
- 21:22Auto-generating observability docs
- 23:58Rate limiting and quotas
- 25:02Diagnosing latency issues
- 26:53Database connection problems
- 28:43Correlating traces and logs
- 30:12Unified instrumentation benefits
- 31:17Slow MongoDB queries
- 32:00Using AI for observability
- 36:02Summary of fixes
- 37:07Live instrumentation demo
- 49:02Q&A on OpenTelemetry
related talks
53mUnmask hidden issues with Observability superpowers!
48mObservability of Your Application
45mObservability for Modern Spring Applications
51mI Can See Clearly Now: Observability of JVM & Spring Boot 2-3-4 apps
38mObservability 101 with Spring and Micrometer
59mTo Production and Beyond: Observability for Modern Spring Aps
55mDemystifying Observability for Spring Applications
19mOops my app performance sucks... what if observability could be a game changer?