281 WJUG - Tracing Issues in Your Application

"Tracing Issues in Your Application"

BUG is BAD

BUG on PRODUCTION is BADDER

BUG on PRODUCTION that we cannot TRACK and SOLVE is THE BADDEST

We don't like BAD, but BADDEST is wrong beyond explanation (not only grammatically speaking).

Marcin Grzejszczak, a man of many talents, named and unnamed, will show us how to be one step ahead of the bugs, track them down and exterminate as effective as possible.

START 19:00 CET on YouTube:

https://www.youtube.com/watch?v=Bgo7dcCbqV8

Abstract:

Imagine that you're receiving a support ticket that your application is not working fine. You read the attached stacktrace and now it's time to solve the mystery - what did the user do that led to 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 via Spring Cloud Sleuth, Tanzu Observabilty, OpenZipkin, OpenTelemetry, and more!

The presentation will consist of some theory but there'll also be live coding and demos.

FOR THE MOST ACTIVE PARTICIPANTS WE HAVE FREE ENTRANCE TO ALL-DAY WORKSHOPS BY STACJA.IT(ALSO YOU CAN USE CODE WJUG10 FOR 10% DISCOUNT), JETBRAINS PRODUCT LICENCES and A MYRIAD OF GREAT BOOKS (sponsored by Decerto)