“Dimensional honesty week changed how we label canary traffic. We stopped mixing it into the customer p95 by accident.”Yuna · Platform engineering · Gwangju
Flagship course
Telemetry to Insight
A six-week rebuild of how you turn metrics, logs, and traces into application analytics for observability dashboards that survive real incidents.
Learning outcomes
- Audit an existing board and remove panels that cannot answer a user question.
- Model golden signals with region and release dimensions that fit Korean multi-region patterns.
- Wire traces and logs as supporting evidence, not competing walls of text.
- Publish a narrative dashboard with runbook links and a critique-ready title system.
Informational pricing
₩640,000 / person in Dashboard Studio
Also available as a single-course seat at ₩520,000. No online checkout — contact us to enroll. See pricing paths and the refund policy.
Modules
- Signal inventory — Catalog what you collect versus what incidents actually need.
- Panel language — Titles, units, and annotations that read under fatigue.
- Dimensional honesty — When to facet by region, version, or customer tier — and when not to.
- Trace bridges — Connect a spike to the span that explains it.
- Stakeholder boards — One board for ops, one for product, sharing the same definitions.
- Ship & critique — Publish, gather peer notes, and schedule the next prune.
Instructor
Sora Lim
Former platform lead for a Seoul commerce stack. Sora designs Observacloud labs around boards that already exist — she would rather improve your Tuesday dashboard than invent a demo utopia.
Course reviews
“Strong critique culture. I wanted more OpenTelemetry collector deep-dives; the course stays at the analytics layer on purpose.”Marcus · Remote cohort
FAQ
Do I need a specific monitoring vendor?
No. Labs use vendor-neutral patterns. You will adapt examples to Grafana, Datadog, CloudWatch, or similar. We do not teach every UI click-path.
What is a real limitation of this course?
Telemetry to Insight does not cover building collectors or agent fleets. If your telemetry pipeline is broken, fix that first — or join Observability Lab for a facilitated sprint that can include pipeline triage.
How much weekly time?
Plan for about five hours: one live lab, two async exercises, and a short critique thread.
Is there a certificate?
Yes — issued after you publish your narrative board and complete the peer critique.
Ready for a calmer board?
Ask about the next Dashboard Studio cohort or a private Observability Lab.