Serving, containers, and resources · Lesson 2 of 17 · 8 min

Read gateway logs

Gateway logs help connect request failures with component state. Keep the request identifier and error category; do not infer root cause from severity alone.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the case evidence
Read /opt/ai-lab/cases/aiops-serving-resources-002.json. Separate the recorded facts from your assumptions.
Hint & worked example
Gateway logs help connect request failures with component state. Keep the request identifier and error category; do not infer root cause from severity alone.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-serving-resources-002.json
```
Common mistake to avoid: Prompt wording causes a TCP connection refusal.
2
Isolate the deciding signal
Select the error field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Check the runtime listener on port 8090 before rewriting the prompt.
A successful JSON query isolates error.
```
jq .error /opt/ai-lab/cases/aiops-serving-resources-002.json
```
Common mistake to avoid: Using a different case or an unrelated signal as the justification.
3
Record your operational decision
Choose the justified code: check-upstream-listener, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-serving-resources-002-decision.txt.
Hint & worked example
Check the runtime listener on port 8090 before rewriting the prompt.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'check-upstream-listener' > /home/learner/lab/aiops-serving-resources-002-decision.txt
```
Common mistake to avoid: Prompt wording causes a TCP connection refusal.

Understand the pattern

Gateway logs help connect request failures with component state. Keep the request identifier and error category; do not infer root cause from severity alone.

Interpret the evidence

Check the runtime listener on port 8090 before rewriting the prompt.

A tempting mistake

Prompt wording causes a TCP connection refusal.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result

$ cat /opt/ai-lab/cases/aiops-serving-resources-002.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "request": "req-27",
  "error": "upstream connection refused",
  "upstream": "127.0.0.1:8090"
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .error /opt/ai-lab/cases/aiops-serving-resources-002.json

"upstream connection refused"

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'check-upstream-listener' > /home/learner/lab/aiops-serving-resources-002-decision.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “check-upstream-listener” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Read gateway logs” justify?Check the runtime listener on port 8090 before rewriting the prompt.Prompt wording causes a TCP connection refusal.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Prompt wording causes a TCP connection refusal.” What should you do?Accept it because the training command completed.Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: List training containers Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

Case methodology: evidence, limits, decision