Observability
Production Telemetry Design for Microservices
Instrument services without drowning operators: RED metrics, exemplars, trace budgets, and alert fatigue reviews grounded in your dashboards.
3 days, virtual · Virtual cohort · starts
₩2,600,000 · informational reference only
Program narrative
This course program walks teams through telemetry design that respects cardinality limits and on-call realities. You will compare tracing strategies, logging policies, and business-level SLOs that survive reorgs.
What is included
- Cardinality budgeting workshop
- Trace sampling games with realistic traffic mixes
- Log schema linting examples
- Dashboard critique with annotation layer
- Runbook starter aligned to incident retros
- Cost projection worksheet for observability vendors
- Leadership readout template for risk owners
Outcomes
- Publish a service-level telemetry contract for three critical paths
- Agree on alert ownership and suppression windows
- Reduce duplicate signals called out in the lab critique
Ravi Menon
DevOps lab engineer specializing in humane on-call rotations.
Participant questions
We stay vendor-neutral in exercises; bring screenshots or JSON exports and we adapt.
Recent participant notes
Telemetry Design Lab reframed how we talk about exemplars with product teams. Some modules felt dense for newcomers—that pace matched our advanced group.
Liked the cardinality budgeting sheet; we adopted it immediately.