Distributed Telemetry Mastery
An eleven-week flagship for reading application analytics across distributed clouds — so efficiency work becomes a practiced craft, not a quarterly scramble.
What you will walk away with
- A repeatable method to attribute region cost to application paths
- Lab notebooks for latency drift, idle pools, and release-train spikes
- Facilitation scripts for efficiency reviews across product and SRE
- A personal Signal Map artifact for one production service family
Informational price for the open cohort: ₩1,890,000 per seat. Private fleets use Continuous Efficiency pricing.
Modules
Each week pairs a short lecture with a lab you can run on staging.
Metrics, traces, and logs as narrative — not three separate religions.
Map user journeys across AZs and clouds; spot drift before finance does.
Find capacity that looks healthy and still spends. Includes a real limitation workshop.
Tie deploys to cost and latency anomalies with gentle change-management habits.
Run an efficiency review that leaves the room aligned, not defensive.
Present your service family’s analytics story and recommended efficiency bets.
Instructor
Hana Seo
Former observability lead for a Korea-based multi-cloud commerce platform. Hana teaches with soft structure: fewer slides, more annotated traces, and feedback that respects how busy fleets really are.
FAQ
Do I need a specific cloud vendor?
No. Labs use vendor-neutral patterns. You will need access to some telemetry export from at least one environment.
Is there a real limitation I should know?
Yes. We do not provide live production access to your systems, and we cannot guarantee a specific cost reduction percentage. Outcomes depend on how candid your telemetry is and how much change authority your team has.
Can finance partners join?
Encouraged for weeks 9–11. Earlier weeks stay technical so engineers can move quickly.
How is this different from a tooling course?
We teach judgment around application analytics for distributed cloud efficiency. Tools change; the reading habits transfer.
Learner notes
“The Idle & Warm Waste module caught a canary fleet we had forgotten. Capstone feedback was specific about our trace sampling gaps.”
Short and honest: week six homework collided with our on-call rotation, so I fell behind. The facilitators still reviewed my late Signal Map without making it weird.