Observability

Observability Handoffs for Platform Teams

Trace, metrics, and log contracts that survive on-call rotations and vendor changes.

Duration: 4 weeks
Format: Online-first
Level: Advanced
Schedule: Intensive week

7.400.000 ₫

Informational tuition reference — see Money-Back Policy for eligibility.

Industrial sensors and monitoring equipment in a clean facility

Syllabus depth

Observability is treated as an interface between dev and platform. You will design metric namespacing, trace propagation headers, and log schemas that SREs can query under stress. Labs include OpenTelemetry wiring for a sample service and a postmortem writing clinic focused on data gaps, not blame.

Feature focus

RED and USE signals tailored to batch and online paths
Trace context propagation across async boundaries
Log schema workshop with JSON field contracts
Dashboard review rubric used by mentors
Sampling strategies that preserve error traces
Alert fatigue exercise with real noisy graphs
Runbook links embedded in alert annotations

Outcomes

Publish a telemetry checklist for a service you own
Implement tracing on a sample API with mentor approval
Draft an alert tuned to symptom, not cause

Mentor on record

Quang Vo

Observability coach who led a Grafana/Prometheus rollout for a fintech ledger.

Field notes

“Short course, dense. Observability Handoffs forced our team to name log fields before coding dashboards.”

Mai · Da Nang

“Quang’s alert critique hurt a little—in a useful way. We retired three paging rules that never matched user pain.”

Phuc · Platform engineer · EdTech scale-up · survey

Cohort FAQ

Examples use Prometheus-compatible stacks; vendor-specific agents are discussed comparatively.