Troubleshoot Your RoR Microservices with Distributed Tracing
summary
Shows a working implementation that instruments Rails with OpenCensus and exports traces to backends like DataDog service map, using Rack and Faraday middleware to propagate trace and span IDs. Claims it runs across about 100 microservices in Ruby Go Python Node and Rust and yields per-request traces that list involved services, latency per span, SQL and template spans, and causality so teams locate surprising bottlenecks and root causes quickly.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:53Why You Need Distributed Tracing
- 10:42Distributed Tracing
- 12:04Service Map
- 14:09Open Census
- 28:42Open Tracing
related talks
31mUnderstanding Microservices with Distributed Tracing
34mDebugging Your Services with Distributed Tracing
30mDistributed Tracing: From Theory to Practice
38mDistributed Tracing: Practices, Patterns & Technologies for Debugging Microservices
24mDistributed Tracing : New DevOps Foundation.
30mDebugging Large Scale Service Oriented Systems
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
36mDistributed Tracing: From Theory to Practice
