How can we leverage observability to deal with legacy code?
This question is among those most often asked by new observability practitioners. The answer is, unfortunately, more nebulous. Modern observability tools offer so much to help keep fresh code, well, fresh. That’s great news for greenfield code, but most code sooner or later succumbs to the woes of time and team churn. How do you apply observability to code that hasn’t been instrumented since day one?
Isobel Redelmeier explores how to use tracing and other observability practices to tame legacy spaghetti. No team has infinite time or hands, and observability can help you figure out where your limited resources can have the most impact. Join in to learn how to determine critical paths and low-hanging performance fruit.
Isobel Redelmeier works on open source software at LightStep, where she focuses on OpenTracing and other observability solutions to improve performance management across distributed systems. She learned firsthand how difficult, and how valuable, observability can be when working at Pivotal, where she pushed code in about 10 languages to different production systems while working with Pivotal Labs. She later focused on security in Cloud Foundry.
For exhibition and sponsorship opportunities, email SAconf@oreilly.com
For information on trade opportunities with O'Reilly conferences, email email@example.com
View a complete list of O'Reilly Software Architecture contacts
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org