Skip to content
Clairos Learn

AI systems foundations · Lesson 10 of 15 · 9 min

Locate an operational failure

Locate the first boundary that failed. An HTTP request rejected by a gateway has not necessarily reached the model, so inspect the gateway error before changing generation parameters.

Open the labCourse map
Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Locate the first boundary that failed. An HTTP request rejected by a gateway has not necessarily reached the model, so inspect the gateway error before changing generation parameters.

Interpret the evidence

Fix the request envelope; this request never reached the runtime.

A tempting mistake

Increase the model context window to fix a missing JSON field.

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-systems-foundations-010.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "http_status": 400,
  "reached_runtime": false,
  "error": "missing messages"
}

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

$ jq .reached_runtime /opt/ai-lab/cases/aiops-systems-foundations-010.json
false

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

$ printf '%s\n' 'fix-envelope' > /home/learner/lab/aiops-systems-foundations-010-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 “fix-envelope” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Locate an operational failure” justify?

Apply it elsewhere

A colleague concludes: “Increase the model context window to fix a missing JSON field.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Read a system dependency mapTry 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

  1. 01Separate data and instructionsRetrieved documents are data, not trusted instructions. Keep the application policy separate and do not let a quoted document authorize tools or change the user task.Practice
  2. 02Read a system dependency mapDependencies form a directed map. A failed shared dependency can affect several healthy callers; confirm the dependency evidence instead of restarting every caller.Practice
  3. 03Define an operator signalAn operator signal names a quantity, unit and observation window. A bare latency number cannot support an incident claim until its aggregation and time range are clear.Practice

Case methodology: evidence, limits, decision