Many engineering organizations have now adopted microservices or other loosely coupled architectures, often alongside DevOps practices. Together these have enabled individual service teams to become more independent and, as a result, have boosted developer velocity. However, this increased velocity often comes at the cost of overall application performance or reliability. Worse, teams often don’t understand what’s affecting performance or reliability – or even who to ask to learn more. Distributed tracing was developed at organizations like Google and Twitter to address these problems and has also come a long way in the decade since then.

In this talk, we’ll cover the fundamentals of distributed tracing and show how tracing can be used to:

  • Accelerate root cause analysis and make alerts more actionable
  • Understand a distributed system and improve communication among teams
  • Prioritize engineering work by putting it in the context of end user experience
  • Hold teams accountable using service level objectives (SLOs)

By the end of this presentation, you’ll understand why distributed tracing is necessary and how it can bring performance and reliability back under control.

Wednesday August 19th, 2020 11AM PST, 2PM EST, 6PM GMT

Brought to you by: