Andrii Shabalin, a Site Reliability Engineer at an unnamed company, gave a presentation on distributed tracing for microservices using Jaeger. Jaeger is an open source distributed tracing system released by Uber Technologies that can be used for monitoring, troubleshooting, and analyzing the performance of microservices-based distributed systems. Shabalin discussed how Jaeger works, how to instrument applications to generate traces, and how to deploy and monitor Jaeger. He provided examples of how to propagate tracing context between services and demonstrated Jaeger's capabilities.

1. About speaker
Name: Andrii Shabalin
Role: Site Reliability Engineer
Company:

2. Distributed tracing for
microservices with Jaeger

3. What is Jaeger?

4. Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing system
released as open source by Uber Technologies. It is used for monitoring and
troubleshooting microservices-based distributed systems
https://www.jaegertracing.io/docs/1.17/

5. What is Jaeger for?

6. Distributed transaction monitoring
Performance and latency optimization
Root cause analysis
Service dependency analysis
Distributed context propagation
https://www.jaegertracing.io/

7. Do we really need all this things?

8. Definitely, if your application’s architecture like in Uber ↓

9. Tracing types

10. 1. Cross-process tracing
2. Database tracing
3. In-process tracing

11. How to deploy, operate
& monitor Jaeger?

12. https://hub.docker.com/u/jaegertracing
Jaeger provides Kubernetes operator:
https://github.com/jaegertracing/jaeger-operator
Jaeger components are released as Docker images:
https://www.jaegertracing.io/docs/1.17/deployment/

13. https://github.com/jaegertracing/jaeger/blob/master/m
onitoring/jaeger-mixin/dashboard-for-grafana.json
https://www.jaegertracing.io/docs/1.17/monitoring/

14. How Jaeger works?

15. https://www.jaegertracing.io/docs/1.17/architecture/

16. https://www.jaegertracing.io/docs/1.17/architecture/

17. What is “traces”?

18. ● TRACE
● SPAN
● SPAN CONTEXT
The description of a transaction as it moves through a distributed system.
A named, timed operation representing a piece of the workflow.
contains data that the tracing system needs to propagate to the downstream service

19. https://www.jaegertracing.io/docs/1.17/architecture/

21. How to get traces?

22. 1. Hand-made Instrumentation of
your application
2. Configuration of already
instrumented software

23. How to made
instrumentation?

24. OpenTracing - is set of APIs, libraries and specifications
https://op entracing.io/docs/overview/what-is-
tracing/

25. https://github.com/opentracing/opentracing-go https://github.com/jaegertracing/jaeger-client-go

26. Distributed tracing,
OpenTracing, Jaeger. What
the difference?

27. 1. Distributed Tracing - is method/approach
1. OpenTracing - is set of APIs, libraries and
specifications
1. Jaeger - is a infrastructure layer which store and
process data which corresponding OpenTracing
specification

28. What software already
support tracing out of the
box?

29. Service Proxy API Gateway Service Mesh

30. So why I should do
applications instrumentation
if service mesh could care
about tracing?

31. 1. If you want to know about
performance inside application
2. If you services communication is not just
response/replay over http

32. req.Header.Add("x-request-id", r.Header.Get("x-request-id"))
req.Header.Add("x-b3-traceid", r.Header.Get("x-b3-traceid"))
req.Header.Add("x-b3-spanid", r.Header.Get("x-b3-spanid"))
req.Header.Add("x-b3-parentspanid", r.Header.Get("x-b3-parentspanid"))
req.Header.Add("x-b3-sampled", r.Header.Get("x-b3-sampled"))
req.Header.Add("x-b3-flags", r.Header.Get("x-b3-flags"))
req.Header.Add("x-ot-span-context", r.Header.Get("x-ot-span-context"))

33. Tears and disper of
microservice observability...

34. 1. TCP 2. Message Buss

35. Demo time!

36. THANKS!
https://www.linkedin.com/in/andrii-shabalin/