Learn how to troubleshoot complex microservice environments with Jaeger and Zipkin, two popular tracing projects, and how to evaluate the performance of a complex application.
Overview
Syllabus
Introduction
- Tracing for observability
- Your lab and test app
- Testing the setup
- Why do we need distributed tracing now?
- Tracing libraries and agents
- Overview of Zipkin and Jaeger
- Configuring the Zipkin tracer
- Tracing app code
- Seeing the app trace in the Zipkin UI
- Adding metadata to your traces
- Seeing the tags and error event in the Zipkin UI
- Tracing database calls with Zipkin
- Seeing the database traces in the Zipkin UI
- Tracing message queue calls
- Seeing the message queue traces in the Zipkin UI
- Tracing web calls server-side
- Seeing web service traces in the Zipkin UI
- Tracing web calls end-to-end
- Seeing the whole picture
- Configuring the Jaeger tracer
- Tracing app code
- Seeing the app trace in the Jaeger UI
- Adding metadata to your traces
- Seeing the tags and error event in the Jaeger UI
- Tracing database calls
- Seeing the database traces in the Jaeger UI
- Tracing message queue calls
- Seeing the message queue traces in the Jaeger UI
- Tracing web calls server-side
- Seeing web service traces in the Jaeger UI
- Tracing web calls end-to-end
- Seeing the whole picture
- Persisting trace data for long term analysis
- Integrating trace data with the rest of your monitoring systems
- Additional help and resources
Taught by
Peco Karayanev
