Serving, containers, and resources · Lesson 15 of 17 · 6 min

Inspect service dependencies

Dependency checks identify what a service needs to work. Prefer repairing the failing dependency over restarting healthy callers without evidence.

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-015.json. Separate the recorded facts from your assumptions.
Hint & worked example
Dependency checks identify what a service needs to work. Prefer repairing the failing dependency over restarting healthy callers without evidence.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-serving-resources-015.json
```
Common mistake to avoid: Restart both healthy processes before looking at the unavailable index.
2
Isolate the deciding signal
Select the index field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Investigate the required index while preserving healthy gateway and runtime processes.
A successful JSON query isolates index.
```
jq .index /opt/ai-lab/cases/aiops-serving-resources-015.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: repair-index-dependency, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-serving-resources-015-decision.txt.
Hint & worked example
Investigate the required index while preserving healthy gateway and runtime processes.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'repair-index-dependency' > /home/learner/lab/aiops-serving-resources-015-decision.txt
```
Common mistake to avoid: Restart both healthy processes before looking at the unavailable index.

Understand the pattern

Dependency checks identify what a service needs to work. Prefer repairing the failing dependency over restarting healthy callers without evidence.

Interpret the evidence

Investigate the required index while preserving healthy gateway and runtime processes.

A tempting mistake

Restart both healthy processes before looking at the unavailable index.

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-015.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "gateway": "ready",
  "runtime": "ready",
  "index": "unavailable",
  "gateway_requires_index": true
}

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

$ jq .index /opt/ai-lab/cases/aiops-serving-resources-015.json

"unavailable"

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

$ printf '%s\n' 'repair-index-dependency' > /home/learner/lab/aiops-serving-resources-015-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 “repair-index-dependency” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Inspect service dependencies” justify?Restart both healthy processes before looking at the unavailable index.Make the change now and gather the missing evidence afterward.Investigate the required index while preserving healthy gateway and runtime processes.

Apply it elsewhere

A colleague concludes: “Restart both healthy processes before looking at the unavailable index.” What should you do?Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.Accept it because the training command completed.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Prepare a rollout review 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