Becoming a cloud-native physician: Using metric and traces to diagnose applications
summary
Argues that adding trace context to metrics makes diagnosis practical and shows how to instrument Java services end to end: uses OpenTelemetry via MicroProfile Telemetry on Open Liberty, exports to Jaeger. Builds two small microservices (system and inventory), enables automatic tracing with a server.xml flag and mpcfg property, demonstrates manual @WithSpan instrumentation and optional Java agent, and shows traces appearing in Jaeger — minimal code change, working demo.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:27Why cloud-native physicians
- 5:00Observability fundamentals
- 7:25Logs metrics and traces
- 13:21Open Liberty and microprofile
- 19:20OpenTelemetry explained
- 29:17Demo setup and environment
- 36:11Automatic instrumentation demo
- 40:22Manual instrumentation overview
- 45:43Conclusion and resources
- 46:51Q&A
related talks
38mBecoming a cloud-native doctor
47mUsing metric and traces to diagnose our cloud-native applications
47mThrough the Looking Glass: Effective Observability for Cloud-Native Applications
58mThrough the looking glass: Effective observability for cloud native applications
37mThrough the looking glass: Effective observability for cloud native applications
52mPerfecting reliable code delivery for the cloud
37mMake your Java application observable with no code changes using OpenTelemetry
41mModern Application Debugging: An Introduction To OpenTelemetry