Read me firstWhat this document is
Goals & non-goals
This is the spec / acceptance contract for the curriculum, not the day-by-day timeline (that artifact lives separately). It defines what "done" means at every phase gate, how the certs sequence, and what the capstone must survive. Read it as the rubric a hiring panel — or a future you — would grade the program against.
Goals
- Reach production-operator depth on the full Grafana LGTM + OpenTelemetry + eBPF stack, not tutorial-level familiarity.
- Ship one self-contained GitHub repo per lab — runnable by a stranger via README +
docker compose upormake. - Pass 4 certifications in priority order (PCA → OTCA → CKA → CCA) as forcing functions, not as the goal itself.
- Be able to debug a real incident using telemetry alone — no SSH, no print statements, no guessing.
- Build interview-grade artifacts and OSS contributions that demonstrate the work publicly.
Non-goals
- Not a survey of commercial SaaS consoles (Datadog/New Relic UI clickthroughs); concepts transfer, vendor UIs do not.
- Not re-teaching Node.js, Kafka, Kubernetes, or AWS fundamentals — those are assumed.
- Not a frontend/RUM deep-dive; browser telemetry appears only where the capstone touches it.
- Not chasing every signal vendor — depth on OSS reference implementations over breadth.
- Not a certification-cram; certs validate the hands-on work, they do not replace it.
The work, phase by phase11 phases · one repo each
Forcing functionsCertification plan
Certification plan
Certs are sequenced so each exam lands at the end of the phase that prepares it, with a buffer day. They validate the lab work rather than driving it.
| Priority | Cert | Full name | ~Exam day | Prepared by phase |
|---|---|---|---|---|
| 1 | PCA | Prometheus Certified Associate | ~Day 20 | P2 — Metrics (Prometheus & Mimir) |
| 2 | OTCA | OpenTelemetry Certified Associate | ~Day 55 | P5 — OpenTelemetry & Collector |
| 3 | CKA | Certified Kubernetes Administrator | after P6 window | P6 — Kubernetes Observability |
| 4 | CCA | Cilium Certified Associate | after P8 window | P8 — eBPF & zero-code (Beyla/Cilium) |
PCA and OTCA are tightly time-boxed inside their phases. CKA and CCA are broader and may schedule after Day 100 — see Risk R1.
Day 100Capstone acceptance criteria
Production capstone — acceptance criteria
A realistic e-commerce flow: Frontend → API Gateway → Order → Inventory → Payment → Kafka → Workers → PostgreSQL → Redis, instrumented with all four signals plus Beyla eBPF, deployed up a progressive target ladder, load-tested with k6, paged via OnCall, and governed by SLOs. The capstone is accepted only when every box below is true.