SREcon18 Americas - Distributed Tracing, Lessons Learned

Gina Maini, Jet.com
Your engineering job might look something like this:
1. Understand dependencies.
2. Keep the site up.
3. Understand where you messed up.
Distributed Tracing helps you with all of these. Industry standards like OpenTracing provide some mindshare on tracing RPC style communications, but leave much unsaid about asynchronous communications over message busses or Kafka. At Jet.com we use Kafka and Event Sourcing at nearly every tier of our architecture, so tracing these types of communications motivated us to create our own protocol and semantics around operations and channels. We learned a lot from creating our own libraries in F# and on-boarding engineering teams around our company to try tracing their communications. We learned a lot and are here to share tips, tricks, and hard earned lessons.
Sign up to find out more about SREcon at srecon.usenix.org