Skip to main content
A trace records every step of a request through your agent, so when a response is wrong you can see which step caused it.

​
What the command does

It asks which coding agent to use, then what to trace:
  1. An existing app
  2. A new starter app
  3. Your coding agent
It then installs the AX CLI and skills, instruments your app, and runs it until the first trace arrives, asking before it changes anything. Add your LLM provider’s API key, such as OPENAI_API_KEY, to the same .env. See one command setup for details.
Instrument Manually view showing the integration picker with 30+ providers and frameworks
Most often the LLM provider key is missing. If See your first trace in Tracing Projects still shows No traces yet after about 45 seconds, check:
  1. API key: look for 401 or StatusCode.INTERNAL in your terminal.
  2. Space ID: a wrong ID sends traces to another space.
  3. Endpoint: use the HTTP or gRPC endpoint your exporter expects.
  4. Silent failures: BatchSpanProcessor hides exporter errors, so swap in SimpleSpanProcessor to see them.

​
Read a trace

Open your project to see one trace per request.
Traces list view showing app requests
Click a trace to open its span tree. Each span shows its span kind, input, output, latency, and status. LLM spans also show token counts and cost.
Expanded trace for a travel agent: nested agent, tool, retriever and LLM spans with per-span latency and token counts, beside the Input / Output panel showing the system, user and assistant messages
Find a response that came back wrong and check each step. You can look manually, ask Alyx, or ask your coding agent with the arize-trace skill. Next, score every new trace automatically.

Next: Evaluate production traffic

Learn more about Tracing