Building Observable Java Apps that Scale with Quarkus
summary
Hands-on recipe for shipping observable Quarkus services: add Quarkus OpenTelemetry dependency only (traces on by default; metrics and logs must be enabled, JDBC telemetry off by default), point to a collector (Grafana Alloy) that batches and transforms data, and run a self‑hosted LGTM (Loki, Grafana, Tempo, Mimir) stack via docker‑compose. Demo app shows per‑request spans, JDBC SQL spans, custom counters (e.g., user‑create), cost‑per‑request estimates, and dashboards that correlate logs, traces and metrics.
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 1:59What is observability?
- 5:11The power of traces
- 10:13OpenTelemetry as the standard
- 21:11Grafana LGTM stack
- 31:07Why Quarkus?
- 35:09Quarkus OpenTelemetry setup
- 39:26Custom metrics and traces
- 47:11Advanced use cases and demos
- 56:58Q&A and closing
related talks
46mKubernetes. From 0 to Production-Grade with Java.
26mEmpowering Quarkus Applications with AI and OpenTelemetry on Kubernetes
49mKubernetes. From 0 to Production-Grade with Java
42mDistributed Tracing Integration with OpenTelemetry and Knative
34mDistributed Tracing Integration with OpenTelemetry and Knative
28mDistributed Tracing Integration with OpenTelemetry and Knative _ _ _
49mSupersonic subatomic Enterprise Java from the ground up
53mMeet Quarkus