Observability and tracing · Lesson 1 of 15 · 9 min

Read an observability map

Logs, metrics and traces answer different questions. Combine a metric trend with a trace and targeted logs instead of treating any single view as the complete explanation.

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-001.json. Separate the recorded facts from your assumptions.
Hint & worked example
Logs, metrics and traces answer different questions. Combine a metric trend with a trace and targeted logs instead of treating any single view as the complete explanation.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-observability-tracing-001.json
```
Common mistake to avoid: A metric graph alone identifies the exact failing source line.
2
Isolate the deciding signal
Select the trace field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Correlate the slow retrieval span with the index timeout and latency trend.
A successful JSON query isolates trace.
```
jq .trace /opt/ai-lab/cases/aiops-observability-tracing-001.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: correlate-three-signals, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-observability-tracing-001-decision.txt.
Hint & worked example
Correlate the slow retrieval span with the index timeout and latency trend.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'correlate-three-signals' > /home/learner/lab/aiops-observability-tracing-001-decision.txt
```
Common mistake to avoid: A metric graph alone identifies the exact failing source line.

Understand the pattern

Logs, metrics and traces answer different questions. Combine a metric trend with a trace and targeted logs instead of treating any single view as the complete explanation.

Interpret the evidence

Correlate the slow retrieval span with the index timeout and latency trend.

A tempting mistake

A metric graph alone identifies the exact failing source line.

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

{
  "fixture": "Fictional training data; not a live measurement.",
  "metric": "p95 increased",
  "trace": "retrieval span slow",
  "log": "index timeout"
}

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

$ jq .trace /opt/ai-lab/cases/aiops-observability-tracing-001.json

"retrieval span slow"

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

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

Explain it

What does the evidence in “Read an observability map” justify?A metric graph alone identifies the exact failing source line.Make the change now and gather the missing evidence afterward.Correlate the slow retrieval span with the index timeout and latency trend.

Apply it elsewhere

A colleague concludes: “A metric graph alone identifies the exact failing source line.” 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: Inspect gateway metrics 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