PagedAt2AM
No one teaches you this until you're paged at 2am.
Production monitoring and incident response — reading logs, spotting anomalies, making rollback decisions. The skills CS degrees skip.
What you'll learn
Six modules. Short articles, interactive visuals. No certification theater.
Reading logs without drowning
Filtering signal from noise, structured vs unstructured logs, correlating by request ID and timestamp.
Kibana essentials
The 20% of features that cover 80% of debugging.
Grafana essentials
The 4 panels to check first — error rate, latency p99, resource usage, request volume — and how to read them together.
Spotting a memory leak
Sawtooth vs staircase patterns, deploy markers, and why RSS climbing while traffic stays flat is the tell.
The rollback decision
A decision framework — thresholds, blast radius, timing correlation with deploys — when to roll back immediately vs investigate live.
Building a baseline
Why you need to know normal before an incident, not during one.
Who it's for
Software engineers and new SREs who can code but were never formally taught observability. You've shipped features. You've maybe been on-call once and panicked at a Grafana dashboard you didn't build. This is the gap between "I can write code" and "I can keep it running."
Hands-on practice
The lab puts you in front of a simulated dashboard. Toggle between healthy and incident states. Practice diagnosing what's wrong before your phone actually buzzes.