Image unavailable
Monitoring
Observability Signals That Survive On-Call
Monitoring track focused on operability, not vanity charts. You will wire exemplars and practice reading overlapping failures.
- Duration
- 5 weeks
- Format
- Hybrid async + labs
- Level
- Intermediate
- Schedule
- Mixed KST
1,090,000 KRW Informational list price—see Returns & Refunds for eligibility.
Request informationIncluded focus areas
- SLO drafting workshop
- Burn-rate alert tuning
- Trace sampling strategies
- Log cardinality control tactics
- Post-incident metric cleanup checklist
- Runbook peer review
Outcomes you can show a manager
- Ship three alerts tied to user journeys
- Cut noisy pages by prioritizing symptom-based routes
- Document a tracing sampling policy
Straight answers
Vendor tooling?
We demonstrate with Prometheus-compatible stacks; you can map to your vendor.
Honest limitation?
Mainframe and embedded firmware telemetry are out of scope.
Mentor time?
Two 30-minute 1:1s for alert review.
Experience notes
“Burn-rate lab trimmed three duplicate pages without losing the story on latency.”
“Trace sampling doc is now our team default—short, specific, not preachy.”