Demystifying Observability for Spring Applications
summary
Spring Boot 4.1 auto-configures OpenTelemetry and Micrometer so a running app emits JVM metrics, logs, traces and exemplars that link metrics to trace IDs; the demo builds two services (order + mystery-box with Spring AI), ships observability to a Grafana stack (grafana/otel-lgtm image) plus Tempo, Loki, Prometheus and Pyroscope, and shows traces, logs and flamegraphs correlating a 500 error to a slow DB span. Configuration uses Grafana LGTM and OpenTelemetry and the Micrometer observation API to add business metrics and span attributes.
AI-written summary · about
chapters (10)
- 0:00Observability for Spring
- 1:11Observability signals
- 3:41Profiling for performance
- 6:27Traces and spans in systems
- 12:37OpenTelemetry simplifies observability
- 14:45Spring Boot observability
- 21:59Instrumenting with Micrometer
- 32:54Live demo: order service
- 48:03Traces, logs, metrics in Grafana
- 51:53AI dashboards with MCP
related talks
58mObservability Beyond the three pillars with Spring
38mObservability 101 with Spring and Micrometer
59mTo Production and Beyond: Observability for Modern Spring Aps
47mSpring Boot Observability in Practice: Actuator, Micrometer & OpenTelemetry
46mImplementing Observability in Java-Based Projects
45mObservability for Modern Spring Applications
26mSpring Boot Observability
53mUnmask hidden issues with Observability superpowers!