The problem
When an AI app is slow, wrong or expensive, the answer is in its traces. But traces are a wall of numbers until you know what to look for.
How it works
- 01Read the complaint
- 02Open the steps
- 03Blame one
- 04See why
- 05Learn the habit
What was hard
- Each case teaches one habit: read the timeline, check the search, follow the tokens, check the prompt version, look for errors, read the scores.
- “Close” answers — the step where a problem shows, not where it starts — cost no life, and explain the difference.
The result
A few minutes of play that make a real Langfuse trace readable.