Flagship course

Module Performance Studio

Six weeks of instrumentation craft, dashboard critique, and delivery habits for teams who need application analytics for DevOps module performance — not another unused Grafana folder.

Request a seat View Pipeline Lens pricing
Engineer reviewing performance charts

Learning outcomes

  • Define module-level SLIs that map to user-visible work
  • Instrument traces and metrics without drowning collectors
  • Design dashboards that survive a release board meeting
  • Write a short ownership + error-budget runbook

Informational pricing

Included in the Pipeline Lens tier at ₩420,000 per seat. Observatory teams receive eight seats plus office hours. No payment is processed on this site — contact us for invoices.

Weekly modules

  1. 1
    Signal inventory

    Catalog what your module already emits and what questions remain unanswered.

  2. 2
    SLI design

    Choose latency, correctness, and saturation signals that stakeholders recognize.

  3. 3
    Trace wiring

    Propagate context across module boundaries and spot missing spans.

  4. 4
    Dashboard honesty

    Kill vanity panels; keep views that change release decisions.

  5. 5
    Alert pairing

    Attach alerts to owners and error budgets with Alert Hygiene Lab patterns.

  6. 6
    Clinic finale

    Present your module story; revise with peer and instructor notes.

Instructor

Portrait of instructor Sora Han

Sora Han

Former platform lead who spent a decade translating production pain into curricula from Jeollanam-do. Sora facilitates KST clinics and still reviews learner dashboards line by line.

Learner notes

“Week four’s dashboard honesty module forced us to delete panels we liked but never used in incidents. Painful, useful.”

— Derek N., SRE

“Clinic feedback on our cold-start metric was blunt. I wish the workbook had more .NET examples — we improvised — yet the framework transferred.”

— Yuna, Incheon

FAQ

Do I need Prometheus experience?

Basic query literacy helps. Absolute beginners should budget a weekend with our Trace Reading Primer materials before week three.

Is this tool-specific?

Concepts transfer across OpenTelemetry-friendly stacks. Labs use illustrative configs, not vendor lock-in sales pitches.

What is a real limitation of this course?

We do not rebuild your entire observability platform or negotiate cloud contracts. If your collectors are fundamentally undersized, analytics craft alone will not fix ingestion lag — we will say so early.

How do refunds work?

See our Refund Policy for eligibility windows before cohort kickoff.