Distributed Tracing: From Theory to Practice
summary
Heroku describes running an in-house Zipkin deployment (Java app, Docker/Cassandra) and instrumenting Ruby services with rack middleware and Faraday hooks to propagate IDs, sampling traces and send data over HTTP+JSON to collectors. They avoid host agents, add a reverse proxy for basic auth and an OAuth proxy for UI access, warn about PII from custom tags, note Zipkin and Jaeger as main options, and report getting a usable system running in a few months.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:21Understanding the need
- 6:19Tracing theory and history
- 10:07Tracing implementation components
- 13:51Data transport and visualization
- 15:50Code implementation
- 19:35Evaluation checklist
- 29:06Getting started
related talks
36mDistributed Tracing: From Theory to Practice
34mDebugging Your Services with Distributed Tracing
42mAn introduction to distributed tracing and Zipkin
50mDistributed Tracing in the Wild
24mDistributed Tracing : New DevOps Foundation.
29mDistributed Request Tracing
31mTroubleshoot Your RoR Microservices with Distributed Tracing
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems