When an incident strikes, broken correlations between different telemetry signals can lead to dead ends and frustrate your investigations. Even in the best case, aligning traces and logs costs you time when every second matters.

Eli Oshinsky (Staff Software Engineer, PayPal) will present how his team adopted a strategy centered on wide, structured events—adding business context, error details, and critical metadata to APM spans so the information that incident responders need is available when and where they need it most. He’ll demonstrate how this can be done easily, by tapping into existing loggers and intercepting telemetry that you already have in place. He’ll also show how the value extends beyond incident response, into incident prevention by bringing traces directly into pull request reviews so developers can verify instrumentation and behavior changes before they ship code.

Join this session to make your traces more useful during incidents and more helpful to avoid them.