Performance

Observability for Slow Add-to-Bag

You wire browser traces, structured logs, and lightweight dashboards that nontechnical advisors can read. Exercises mimic intermittent API latency spikes.

Self-paced hybrid 3 weeks Weekend blocks Checkout flows
Key visual for Observability for Slow Add-to-Bag

Tuition (planning only)

920,000 KRW

Informational pricing—no checkout on this site.

Facilitator

Avatar for Sana Rahman

Sana Rahman

Reliability coach for omnichannel carts across APAC.

Inside the syllabus

  • OpenTelemetry browser spans for cart clicks
  • Log schema workshops with support-friendly fields
  • Dashboard tiles tuned for incident bridges
  • Sampling strategies to control cost
  • Post-incident narrative templates
  • Mentor review of alert thresholds

Artifacts you keep

  • Ship a tracing recipe for add-to-bag with annotated screenshots
  • Author a support-facing incident one-pager
  • Run a tabletop exercise with mentor feedback

Participant questions

Backend tracing?

We touch conceptual alignment; backend instrumentation stays with your platform team.

Tooling?

Examples use open standards; vendor APMs are discussed comparatively.

Limitations?

No on-call rotations included—documentation focus only.

Recent reflections

Support-facing dashboard tiles reduced noise on our bridge calls—minor gripe: initial JSON samples were US-centric.

Geonwoo Lee · SRE · Hanaro Basket · 4/5 · survey