Observability
Observability Signals in Practice
540,000 KRW list tuition
You build a single service golden signal set, then extend it with SLOs and alert routing that mirror how mature teams annotate context. No toy graphs—only narratives you can defend.
What you work through
- RED metrics baseline with exemplar wiring plan
- Structured logging schema workshop
- Trace propagation lab across two services
- Alert fatigue review rubric
- Runbook starter tied to each signal type
- Noise budget worksheet for paging policy
Outcomes
- Define SLOs with explicit error budgets
- Ship a paging policy doc with escalation paths
- Pair metrics with logs using stable correlation IDs
Mentor
Sora Kim
Lab engineer who keeps shared telemetry sandboxes honest and resettable.
FAQ
What tooling must I install before day one?
You receive a pinned tool matrix (CLI versions, editor plugins, VPN steps). Unsupported legacy OS releases are not included; you need a 64-bit system with admin rights for container runtimes.
How quickly are mentor reviews returned?
We target two business days for written feedback on deployment artifacts. Live sessions are scheduled in the cohort calendar; same-day turnaround is not promised.
Can my employer sponsor a private cohort?
Yes—volume packages include shared activity logs and a dedicated Slack bridge. Pricing follows the published tier sheet; custom SLAs require a separate statement of work.
Reviews
The canary module references the same Helm hooks we ship internally, so I could paste snippets without renaming everything.
Mentor called out my skipped readiness probe before it bit staging. Still wish the Terraform section had one more multi-env example.