Observability and tracing · Lesson 3 of 15 · 6 min

Read latency percentiles

A p95 latency describes a percentile within an observed window. It does not mean that every request or the average request has that latency.

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-003.json. Separate the recorded facts from your assumptions.
Hint & worked example
A p95 latency describes a percentile within an observed window. It does not mean that every request or the average request has that latency.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-observability-tracing-003.json
```
Common mistake to avoid: Call 480 ms the mean latency for every request.
2
Isolate the deciding signal
Select the p95_ms field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Report p95 at 480 ms over five minutes while keeping the median distinct.
A successful JSON query isolates p95_ms.
```
jq .p95_ms /opt/ai-lab/cases/aiops-observability-tracing-003.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: report-latency-percentile, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-observability-tracing-003-decision.txt.
Hint & worked example
Report p95 at 480 ms over five minutes while keeping the median distinct.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'report-latency-percentile' > /home/learner/lab/aiops-observability-tracing-003-decision.txt
```
Common mistake to avoid: Call 480 ms the mean latency for every request.

Understand the pattern

A p95 latency describes a percentile within an observed window. It does not mean that every request or the average request has that latency.

Interpret the evidence

Report p95 at 480 ms over five minutes while keeping the median distinct.

A tempting mistake

Call 480 ms the mean latency for every request.

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

{
  "fixture": "Fictional training data; not a live measurement.",
  "p50_ms": 120,
  "p95_ms": 480,
  "window_minutes": 5
}

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

$ jq .p95_ms /opt/ai-lab/cases/aiops-observability-tracing-003.json

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

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

Explain it

What does the evidence in “Read latency percentiles” justify?Report p95 at 480 ms over five minutes while keeping the median distinct.Call 480 ms the mean latency for every request.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Call 480 ms the mean latency for every request.” 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: Compare throughput signals 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