Observability of Your Application by Marcin Grzejszczak & Tommy Ludwig @ Spring I/O 2023

Spring I/O 2023 - Barcelona, 18-19 May
Slides: docs.google.com/presentation/...
GitHub repo: github.com/jonatan-ivanov/tea...
Imagine that you’re receiving a support ticket that your application is not working. You read the attached stack trace and now it’s time to solve the mystery. What did the user do that led to the throwing of this exception? Is it possible to find all the logs from all the applications that correspond to this user’s business operation?
What if the user is complaining that the system is slow? How can you decide which concrete operation is the culprit? Is there any way to visualize the latency?
Let’s answer these questions by taking a deep dive into application observability using distributed tracing, metrics, and correlated logs with Spring, VMware Aria Operations for Applications (formerly Tanzu Observability by Wavefront), OpenZipkin, OpenTelemetry, and more!

[@hmcyrus]

15:01 the idea of instrumentation in jdbc layer is 🔥🔥🔥

[@datchoob1978]

I’ve watched this at least 3 times now. Absolutely love how these guys presented.

[@gumayuzi939]

This is damn great and the speakers are cool

[@Vishva20]

Duo combo always 🔥.

[@javadahmadzadeh7129]

Apart from the great content, the presentation and the explanation were really great!

[@brownie830]

golden stuff mate

[@kuatospanov6321]

hi, did not find in application sources how traces delivered to tempo collector? Usually it should be defined in springs application property files in management or otel section.