Skip to content
Clairos Learn

Inference requests and APIs · Lesson 10 of 16 · 7 min

Follow a trace identifier

A trace identifier connects spans across component boundaries. Use the shared trace ID and parent relationships to reconstruct one request path.

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

A trace identifier connects spans across component boundaries. Use the shared trace ID and parent relationships to reconstruct one request path.

Interpret the evidence

Join the gateway and retrieval spans carrying trace-07.

A tempting mistake

Join every log line that occurred during the same minute.

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-inference-apis-010.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "gateway_trace": "trace-07",
  "retrieval_trace": "trace-07",
  "unrelated_trace": "trace-08"
}

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

$ jq .gateway_trace /opt/ai-lab/cases/aiops-inference-apis-010.json
"trace-07"

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

$ printf '%s\n' 'follow-trace-07' > /home/learner/lab/aiops-inference-apis-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 “follow-trace-07” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Follow a trace identifier” justify?

Apply it elsewhere

A colleague concludes: “Join every log line that occurred during the same minute.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Compare batch and single requestsTry 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. 01Inspect a request identifierA request identifier ties a client operation to gateway and runtime evidence. Record the identifier rather than copying the whole prompt into ordinary logs.Practice
  2. 02Compare batch and single requestsBatch execution has per-item outcomes. An accepted batch request does not mean every item completed successfully, so preserve item IDs and partial failure details.Practice
  3. 03Read a streaming event shapeStreaming chunks are increments, not necessarily complete messages. Assemble them in order and require the documented completion signal before marking the response done.Practice

Case methodology: evidence, limits, decision