Observability Escape Room: Solve a Bug With Traces, Logs, and Metrics

A service is failing for only some users, and the codebase is too large to read from top to bottom. Teams must use traces, logs, metrics, correlation IDs, and careful hypotheses to find the fault before the clock runs out.

The session teaches how to move between signals: a metric reveals the symptom, a trace narrows the path, a log confirms the decision point, and a small reproduction proves the fix. It is built for people who want observability to feel useful during real pressure.