Better Observability with No Code Changes
summary
Shows how to add meaningful Java tracing without code edits by using the OpenTelemetry Java agent plus a small tool and concrete heuristics. Demonstration uses the Spring PetClinic and a CLI called Flashlight that scans compiled classes and emits agent config. Heuristics flag methods with locking, client calls, and high call/branch counts so you pick candidates; guidance covers risk (too many spans, high-cardinality attributes), testing, and using agent extensions for custom attributes or exporters.
AI-written summary · about
chapters (11)
- 0:00Observability challenges
- 1:11What is observability
- 2:16OpenTelemetry standards
- 3:20Java instrumentation with OpenTelemetry
- 5:06Aspect-oriented instrumentation
- 8:20Instrumentation candidates with Flashlight
- 11:36Flashlight heuristics
- 13:42Strategic instrumentation guidelines
- 17:38Avoid when instrumenting Java
- 18:40Extending OpenTelemetry Java agent
- 20:04Profiling for visibility
related talks
37mMake your Java application observable with no code changes using OpenTelemetry
55mCoding with the lights ON - OpenTelemetry from code to prod
49mDistributed Tracing in Java? OpenTelemetry for the Rescue!
43mPractical Introduction to OpenTelemetry Tracing
01h 10mObservability For (Java) Devs - 2023 Edition
51mFull-Stack Observability: One Tool to Rule Them All
30mInstrument Your Java Applications with OpenTelemetry!
47mThrough the Looking Glass: Effective Observability for Cloud-Native Applications
