arize-trace

Export and analyze Arize traces and spans by ID for debugging LLM applications.

42|7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Arize-ai/arize-skills --skill arize-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arize-trace
Source: https://github.com/Arize-ai/arize-skills/tree/main/skills/arize-trace
Command: npx skills add https://github.com/Arize-ai/arize-skills --skill arize-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of downloading and analyzing trace data from Arize, enabling faster debugging of LLM application issues.

Core Features & Use Cases

  • Export Traces/Spans: Download trace data by ID, session ID, or span ID using the ax spans export and ax traces export commands.
  • Debug LLM Issues: Filter and analyze trace data to identify errors, latency, and other performance bottlenecks.
  • Use Case: If your LLM application is experiencing errors, use this Skill to export all error traces from the last 24 hours, allowing you to pinpoint the root cause.

Quick Start

Use the arize-trace skill to export all error traces from the project 'my-llm-project' for the last day.

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 to debug LLM application errors?

Export Arize traces for debugging LLM errors by using the `ax traces export` command to download data filtered by trace ID, session ID, or span ID for targeted analysis.

Can I filter Arize spans to identify performance bottlenecks in my LLM application?

Yes, you can filter Arize spans to identify performance bottlenecks by exporting span data with the `ax spans export` command, enabling targeted analysis of latency and errors.

What do I need to download trace data from Arize for LLM debugging?

Downloading trace data from Arize for LLM debugging requires the `ax` CLI installed and valid Arize credentials configured to authenticate export commands.

What is the best way to analyze error traces from the last 24 hours in Arize?

Analyzing error traces from the last 24 hours in Arize involves using export commands with filtering capabilities to download project error traces and pinpoint root causes.

Are there limitations when exporting Arize traces and spans for LLM debugging?

Exporting Arize traces and spans for LLM debugging is constrained by requiring the `ax` CLI and valid Arize credentials to execute the export commands successfully.