Week 13 — Lesson 1: Tracing and debugging a graph

3 min

When the NorthPeak agent gives a wrong answer, invoke shows you the end and nothing in between. Which tool ran, with which SQL, and how long the model took are all hidden. A trace is the ordered record of a run, one line per step, that you can read tomorrow. graph.stream(..., stream_mode="updates") gives you every node's update as it happens, and one JSON line per update makes that trace. This lesson covers the move from invoke to stream, the JSONL format, and what the trace of three real questions shows.

Preview — the rest of the lesson is for enrolled readers.

Already enrolled with a code?

Your access is tied to your account, not to this link. Sign in with the same email you used in class: your course is waiting, no need to enter the code again.

Sign inNo account yet? Create one
This lesson is part of the “Week 13 — Observability and model reliability” module

The first modules of the course are open to everyone. For the rest you have three options: buy this course once and for all, subscribe, or enter the code handed out in class.

Are you a student on this course?

The code is tied to your account: sign in or create an account and it will be applied automatically when you come back.

No account yet? Create one