arize-trace

Export and analyze Arize traces and spans for LLM application debugging.

5|6|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/seldo/aiewf-2026-demo --skill arize-trace-seldo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arize-trace
Source: https://github.com/seldo/aiewf-2026-demo/tree/main/.agents/skills/arize-trace
Command: npx skills add https://github.com/seldo/aiewf-2026-demo --skill arize-trace-seldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires arize, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows users to download, export, and inspect Arize traces and spans to understand the behavior of their LLM applications and debug runtime issues.

Core Features & Use Cases

  • Trace Export: Export traces by ID, spans by ID, and sessions by ID.
  • Root-Cause Investigation: Investigate the root cause of errors using the ax CLI.
  • Use Case: If you encounter an error in your LLM application, use this Skill to export the relevant trace and spans, analyze them, and identify the cause of the error.

Quick Start

To export a trace with ID 'trace-123', run the command: ax spans export my-project --trace-id trace-123 --output-dir .arize-tmp-traces.

Frequently Asked Questions about arize-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export Arize traces by ID to debug LLM application errors?

To export Arize traces for LLM debugging, use the ax CLI to run `spans export` with your project ID and trace ID. This downloads the trace data to a specified output directory for root-cause analysis.

How does span analysis help with LLM debugging?

Span analysis helps with LLM debugging by allowing you to inspect individual spans within a trace. This isolates specific execution steps and runtime issues, revealing the exact point of failure within the larger LLM application flow.

Do I need an Arize API key and project ID to download spans?

Yes, you need an Arize API key and a project ID to download spans. These credentials are required to authenticate your requests and scope the trace and span exports to the correct LLM application project.

Can I use the ax CLI to investigate a specific session ID in Arize?

Yes, you can use the ax CLI to investigate a specific session ID in Arize. The tool supports session-level investigation, allowing you to export and analyze all related traces and spans for a user session.

What is the best way to filter Arize spans for performance analysis?

The best way to filter Arize spans for performance analysis is using the built-in filtering and time-range querying options. These allow you to scope span exports to specific periods, isolating runtime behavior and performance bottlenecks.

Why does my LLM application error require trace export for root-cause investigation?

LLM application errors require trace export because traces capture the full execution context. Exporting traces and spans allows you to inspect the exact inputs, outputs, and execution steps to identify the root cause of runtime failures.