Observability · Online
Distributed Tracing Workshop for Go
3 weeks · Morning ICT · Intermediate
Three-week intensive linking spans across services you run locally. Focus on baggage discipline and tail sampling pitfalls.
THB 9,800 listed Refund & Cancellation
What ships in this track
- W3C traceparent drills
- Baggage allowlist pattern
- Tail sampling simulation
- Span link vs parent decision tree
- Trace-driven debugging clinic
- Custom sampler stub in Go
- Attribute budget worksheet
Outcomes you can evidence
- Wire propagation across two binaries
- Author a baggage policy for one domain
- Present a sampling miss case study
Mentor of record
Orathai Suksom
Tracing implementer for payments-adjacent teams; emphasizes budgeted attributes.
Cohort notes
“Baggage allowlist exercise stopped our attribute explosion—small change, big noise drop.”
“Tail sampling simulation felt abstract until mentors mapped it to our peak hour—then it clicked.”
Straight answers
Vendor?
OTel-first; exporters vary by lab week.
Short course caveat?
Three weeks means tight homework; expect 6–8 hours weekly.
Not covered?
Browser RUM stitching is mentioned only briefly.