Looking for a specific timezone? We have it covered...
View analytic
Wednesday, October 25 • 00:00 - 00:45
Scenario Logging for Effective Telemetry and Retention Analysis

Sign up or log in to save this to your schedule and see who's attending!

Software today is more complex than ever,and our ability to analyze it is limited by our telemetry and monitoring frameworks. Scenario logging provides a way to record a chain of events from a single starting point to one optional end,giving us a way to gain insights on the dynamics of our software.

“Irreproducible bugs become highly reproducible right after delivery to the customer.”
— Michael Stahl’s derivative of Murphy’s Law

Is it possible to reduce the number of bugs being closed as “not repro”?

We’ve all seen it before: customer bugs describe a product behavior previously believed to be impossible, and no amount of time spent in logs or dashboards will provide a clue to how the user got to that state. In search of information, we try to reproduce this behavior in the lab, usually with no success.

Contrary to developers’ popular belief, irreproducible bugs exist outside the imagination of testers and users, signaling warning signs of blind spots and dead ends in our software.

Wouldn’t you just love to have all the information needed already in the logs? And even more, have a way to find other customers facing the same issue and not complaining? If you had a way to achieve that you wouldn’t need to try and reproduce the bug.

By adding scenario logging to these problematic flows not only we’ll be able to investigate and fix these bugs faster, but also be able to identify them earlier and analyze the impact on the user experience.

Scenario logging is designed to log the user’s activities from the moment the user enters the initial state until reaching one of the expected final states, be it success or failure. Using these logs, we can find in which step the user diverted from the expected flow and how, making the fix very simple (blocking that route). More importantly we can also use scenario logging to identify unexpected flows in cases where the user didn’t notice the problem until later or decided not to report it.

avatar for Renana Yacobi

Renana Yacobi

I have been working for over 9 years in leading startups as a senior server-side software engineer, providing solutions in areas such as data mining, operating systems and image processing, specializing in distributed and high performance computation. | 3.5 years ago, when chal... Read More →

Wednesday October 25, 2017 00:00 - 00:45
Continuous Everything: USA/West Coast