Observability
Tracing Journeys for Service Owners
Follow requests across async queues and RPC hops without drowning in span noise.
₩1,580,000 reference tuition
Program narrative
You stitch together traces that cross message brokers and cron bursts, then design guardrails so future engineers inherit readable graphs. Includes exercises on trace-driven debugging during deploys and canarying.
What is included
- Context propagation through worker pools
- Sampling policies that survive deploy windows
- Span attributes that help support teams triage faster
- Debugging stuck consumers with trace breadcrumbs
- Mapping retries without exploding cardinality
- Pairing traces with structured logs without duplication
- Interview walkthrough of a complex trace story
Outcomes
- Tell a coherent cross-service story using three spans or fewer
- Pick sampling defaults that survive Black Friday-style drills
- Teach juniors how to read a waterfall without intimidation
FAQ
Kafka and Rabbit patterns are covered; others use analogous exercises.
Participant notes
Retry cardinality lab finally convinced our org to fund tail sampling.
Still wish we had one more session on browser-side traces, but the backend depth was excellent.