Untangling the knots with distributed tracing
You're sick of grepping through logs, hunting down the cause of last night's outage. Your team dreams of refactoring to better architecture but struggles to get started amid the spaghetti code. Production meets all performance objectives only because you can't measure it. Join Isobel Redelmeier to learn how to apply distributed tracing for better debugging, performance analysis, and refactoring.
|Talk Title||Untangling the knots with distributed tracing|
|Speakers||Isobel Redelmeier (LightStep)|
|Conference||O’Reilly Open Source Software Conference|
|Conf Tag||Fueling innovative software|
|Date||July 15-18, 2019|
You’re sick of grepping through logs all day, hunting down the root cause of last night’s outage. Your team dreams of refactoring to a better architecture but struggles to get started amid the mountain of spaghetti code. Your production meets all performance objectives only because you can’t even measure it. Distributed tracing can help you solve all of these problems (and more). But before you can leverage tracing in your code, you first need to actually add the tracing. Join Isobel Redelmeier to learn how to instrument an existing code base. You’ll start somewhere several levels worse off than “Hello, world” with a ball of mud more akin to reality than the greenfield slate so many tutorials seem to think everyone is perpetually blessed with and discover how to instrument not only your own code but also your favorite libraries and frameworks out there. The session uses Python, but the concepts should be equally applicable to your preferred language.