Lesson 2 of 4 · Free to read
Exercises
Exercises — Platform Observability: Cost, Governance, as-Code
Watch & learn
Course video
Course video
Keep a lab notebook: hypothesis → command → result. Speed without evidence is not a skill.
How to use this file
- Work Lab A → B → C on the same
orders-labrepo - Prefer Docker Desktop; use Kind when the lab says so
- Definition of Done at the bottom is the phase gate
Lab A — Cost & cardinality budget
Time: 45–60 min
Goal: Written budget with enforcement ideas.
Setup
Metrics from earlier phases.
Steps
- List top series by cardinality.
- Set soft/hard limits for metric labels and Loki labels.
- Propose Collector filters for violators.
Success criteria
-
cost-budget.mdcommitted
If stuck
Use Prometheus /api/v1/status/tsdb or cardinality dashboards if available.
Lab B — Obs-as-code
Time: 60 min
Goal: Dashboard + alert YAML/JSON in Git.
Setup
Working Grafana/Prometheus.
Steps
- Export a dashboard JSON.
- Keep PrometheusRule in repo; apply via kubectl/helm.
- Add CI check that YAML parses.
Success criteria
- Git history shows dashboard/rule
- CI lint passes
If stuck
Start with one dashboard — don’t boil the ocean.
Lab C — Golden path pack
Time: 45–60 min
Goal: Templates another team could copy.
Setup
Phase 05 Operator knowledge.
Steps
- Create
golden-path/with README + Instrumentation + ServiceMonitor + Collector fragment. - Write “when to use SaaS” one-pager.
- Peer-review with a classmate/mentor.
Success criteria
- Pack usable by a stranger
- Tradeoff doc exists
If stuck
Clarity > cleverness — copy-paste success is the metric.
Stretch goals
- Sketch multi-region telemetry routing (local Collector → regional gateway)
Definition of Done
- Cost budget written
- At least one asset as code
- Golden path pack reviewed
Exercises — Platform Observability: Cost, Governance, as-Code.