Observability · Online
Observability for Go Services
5 weeks · Weekend intensives · Intermediate
Five-week sprint on OpenTelemetry hooks, exemplars, and RED dashboards for Go microservices. You instrument a sample checkout flow, then tune cardinality with mentors who have run regional traffic.
THB 14,900 listed Refund & Cancellation
What ships in this track
- OTel SDK wiring patterns
- Histogram bucket design workshop
- Log field naming rubric
- Trace tail sampling exercise
- Grafana board templates
- Noise budget worksheet for attributes
- Latency SLO drafting session
Outcomes you can evidence
- Produce a RED dashboard for one route
- Cut noisy log cardinality by at least one measurable step
- Write a runbook snippet for alert tuning
Mentor of record
Danai Srisawat
SRE manager turned instructor; focuses on honest cardinality trade-offs.
Cohort notes
“Exemplars lab tied metrics to traces in a way our vendor docs never spelled out.”
“Histogram buckets module was blunt about mistakes—appreciated the directness.”
Straight answers
Which vendors are referenced?
We use Grafana-compatible examples; concepts transfer to other stacks.
Are alerts configured for me?
You configure alerts in the lab tenant; nothing is pre-prod for your employer.
Limitations?
Mobile clients and browser RUM are out of scope for this backend-only track.