Observability
A system running in production is a black box until you instrument it. Logs, metrics, and traces are how you see inside it, and alerting and SLOs are how you decide when to act.
What you'll actually learn
A running production system is a black box by default — you can't see inside it, you can only see what it chooses to expose. This track builds that visibility on purpose: instrumenting a real service with logs, metrics, and traces, then using alerting and SLOs to decide which of the signals you're now collecting actually deserve to wake someone up at 3am and which are just noise.
What you'll be able to do
You'll take a service that's "acting weird" with no clear symptom and use its logs, metrics, and traces together to find the actual root cause, instead of guessing and restarting things until it goes away. That's the real job behind the word "observability" — not collecting data, but being able to answer "why is this happening" fast enough for it to matter.
Syllabus
Frequently asked
Roughly 2 hours across 8 hands-on quests — you can go at your own pace and pick up exactly where you left off.
You should be comfortable with CI/CD Pipelines first — the skill tree unlocks Observability once you've cleared those.
Yes — Observability is fully available on the free tier, starting with a free first quest and no payment method required to sign up. Plus and Elite remove pacing limits but don't gate any of the Observability curriculum behind a paywall.
Create a free account and begin your first quest — no card required.
Start free