Flagship course

Telemetry Insight Lab

A six-week studio where you translate infrastructure automation signals into application analytics that survive a skeptical manager review.

Live cohort Korea timezone evenings Informational price: ₩1,120,000
Printed charts and sticky notes on a planning table

What you will practice

  • Map job telemetry to application outcomes without inventing vanity KPIs.
  • Write health briefs that separate automation debt from product defects.
  • Design experiments for retry storms and queue lag with clear stop rules.
  • Critique peer dashboards using a shared evidence rubric.

Informational pricing

₩1,120,000 per seat

Includes mentor hours, critique circles, and certificate. Payment is arranged offline — this page does not collect cards.

Request enrollment

Modules

  • Week 1 — Signal inventory. Catalog existing automation events and decide what never belongs on a leadership slide.
  • Week 2 — Pipeline Signal. Build ratios for success, skip, and silent failure across a sample deploy pipeline.
  • Week 3 — Retry Storm worksheet. Detect cascading retries and draft a containment story for on-call.
  • Week 4 — Narrative Metrics clinic. One chart, one claim — peer critique with product partners invited.
  • Week 5 — Application overlay. Join automation health with user-facing SLOs without double-counting outages.
  • Week 6 — Portfolio brief. Ship a two-page insight pack reviewed against the public rubric.
Portrait of instructor Seo Yoon-ah

Instructor

Seo Yoon-ah spent nine years in platform engineering across Seoul and Jeonju before founding the studio. She still reviews every Portfolio brief personally.

Learning outcomes

By the end you can defend an automation health narrative, explain limitations of your data, and hand product leaders a brief that does not require a translator.

Learner notes

Week 5’s application overlay finally connected our deploy lag chart to checkout errors. The homework took longer than advertised on nights when production was noisy.

Jordan Lee · payments platform

★★★★☆

Solid on narrative craft. Mentors were honest when my first brief over-claimed causality.

Client in logistics tech

FAQ

Do I need a specific observability vendor?

No. Bring exports or screenshots from whatever you already run. We focus on claims and ratios, not product certifications.

Is there a real limitation I should know?

Yes. The lab does not teach you how to instrument greenfield systems from scratch. If you have almost no telemetry today, start with Automation Health Notes or expect extra setup time before week two.

Can my whole team join?

Yes — Fleet Observatory pricing covers shared seats. Contact us for a quote rather than purchasing online.

What language is the cohort in?

Primary materials are English. Office hours can accommodate Korean clarifications when scheduled in advance.