Downloaded 26 times
Uploaded bysoasme
Distributed Tracing
Distributed tracing allows monitoring and troubleshooting of transactions that span multiple services. It involves assigning unique IDs to requests as they pass through services and collecting timing data. Popular distributed tracing systems like Dapper, Zipkin, and OpenTracing use unique trace IDs and span IDs to correlate data from multiple services and timespans. They allow identifying slow or faulty services and transactions.
More Related Content
Distributed Tracing
- 1.
- 2.
- 3.
- 4.
- 5. – wikipedia.org `Tracing(software)` “Insoftware engineering, tracing involves a specialized use of logging to record information about a program's execution. ”
- 6.
- 7.
- 8.
- 9. Possible solution • Blackbox •application-agnostic • low correctness • Unique identifier • application-intrusive • instrumentation for various transports
- 11. Pre-Order Traversal • Logparent entering • Log all children • Log parent leaving
- 12.
- 13. Some infrastructure • HTTP:X-Header • Thrift: add tracer • RPC: god-mode • ...
- 14. Clock skew central problemof distributed system
- 15. Things worth mentioned •sampling • reporting • aggregate analysis
- 16.
- 17. Annotation string data associatedwith particular timestamp, service, host, ...
- 18. Annotation Types • cs:client start • sr: server receive • ss: server send • cr: client receive • other: further insight of service
- 19. Span A set ofannotations, represents one specific method call. Has name, id.
- 20. Trace A set ofspan all associated to the same request
- 21. Identifiers • Trace ID •Span ID • Parent ID
- 22. Big Brother Bird •X-B3-TraceId: 64 encoeded bits • X-B3-SpanId: 64 encoded bits • X-B3-ParentSpanId: 64 encoded bits • X-B3-Sampled: Boolean (1/0 • X-B3-Flags: a Long
- 23.
- 24. Some adjustment • scribe-> fluentd + fluentd-plugin-scribe • fiangle -> http-based intrakit • serialization & deserialization annotations
- 25.
- 26.