Observability and tracing · Lesson 15 of 15 · 8 min

Observability checkpoint

A complete observation ties metric, unit, window and scope to a next investigation. Do not combine unrelated signals simply to make a compelling story.

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-observability-tracing-015.json. Separate the recorded facts from your assumptions.
Hint & worked example
A complete observation ties metric, unit, window and scope to a next investigation. Do not combine unrelated signals simply to make a compelling story.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-observability-tracing-015.json
```
Common mistake to avoid: Apply this scoped result to every tenant without checking.
2
Isolate the deciding signal
Select the scope field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Keep the tenant-a retrieval scope explicit when investigating trace-07.
A successful JSON query isolates scope.
```
jq .scope /opt/ai-lab/cases/aiops-observability-tracing-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: keep-scope-explicit, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-observability-tracing-015-decision.txt.
Hint & worked example
Keep the tenant-a retrieval scope explicit when investigating trace-07.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'keep-scope-explicit' > /home/learner/lab/aiops-observability-tracing-015-decision.txt
```
Common mistake to avoid: Apply this scoped result to every tenant without checking.

Understand the pattern

A complete observation ties metric, unit, window and scope to a next investigation. Do not combine unrelated signals simply to make a compelling story.

Interpret the evidence

Keep the tenant-a retrieval scope explicit when investigating trace-07.

A tempting mistake

Apply this scoped result to every tenant without checking.

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

{
  "fixture": "Fictional training data; not a live measurement.",
  "metric": "p95_ms",
  "window": "5m",
  "scope": "tenant-a retrieval",
  "next_trace": "trace-07"
}

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

$ jq .scope /opt/ai-lab/cases/aiops-observability-tracing-015.json

"tenant-a retrieval"

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

$ printf '%s\n' 'keep-scope-explicit' > /home/learner/lab/aiops-observability-tracing-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 “keep-scope-explicit” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Observability checkpoint” justify?Keep the tenant-a retrieval scope explicit when investigating trace-07.Apply this scoped result to every tenant without checking.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Apply this scoped result to every tenant without checking.” 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.

Review this course 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

01Prepare an observability summaryAn observability summary should name the symptom, scope, supporting signals and uncertainty. A concise note is useful only if its key claims can be checked.Practice

Case methodology: evidence, limits, decision