Cloud Code
Menu
Course artwork for Observability Patterns Lab

observability

Observability Patterns Lab

Wire metrics, traces, and logs so on-call rotations read like a story instead of a scavenger hunt.

Intermediate 4 weeks In-person Bangkok intensives Sat full-day

17,200 THB · informational only

Request information

Why this track exists

Hands-on labs rotate through exemplar services where participants tune RED metrics, trace sampling, and structured log fields. Emphasis stays on mentor-led code reads rather than slides.

Inside the studio kit

  • RED metrics tuning sprint
  • Sampling strategy debates
  • Log field taxonomy workshop
  • Shadow on-call dry run
  • Dashboard critique with reviewers
  • Incident warm-up drills
  • Documentation sprint for handoffs

Outcomes you can show

  1. Ship a dashboard PR reviewed by mentors
  2. Document sampling defaults with rationale
  3. Run a tabletop incident using your traces
Avatar for Khemwalee Ruan

Khemwalee Ruan

Technical mentor specializing in telemetry readability.

Cohort murmurs

“Shadow on-call dry run used the same span IDs as week three’s homework. Finally felt coherent.”

Pat · SRE · 5/5 · Google

“Saturday pace is brisk—bring snacks. Worth it for the dashboard critique alone.”

Aom

Straight answers

Do you teach vendor-specific agents?

We reference common agents but labs stay vendor-neutral so teams can map ideas to their stack.

Is on-call shadowing real production?

No. Dry runs use sanitized fixtures; we never attach to your production accounts.

What is not covered?

We skip mobile client crash analytics and marketing funnel tooling.