Paths/DevOps Engineer/Incident Response / Triage Under Pressure
Explain the Upstream Timeouts
Yesterday's application log is full of failed requests. Work out which dependency broke first and write the timeline entry that says so - cause, not fallout.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/incident exists○
- File ~/incident/errors.log holds only the ERROR lines○
- File ~/incident/timeline.md names the failing dependency and the first failure timestamp○
02Walkthrough
1 of 6 revealed- 01
Create the incident folder
The redirect in a later step writes files, but it cannot create directories.
mkdir ~/incident - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list