arize-instrumentation-health

name	arize-instrumentation-health
description	Audits instrumentation health of existing Arize traces. Runs deterministic checks over a bounded span sample (orphaned/uncategorized/duplicate spans, flat structure, blank root I/O, unset status, missing token counts or children) and returns a ranked report. Use when the user asks why traces look empty/flat/broken, wants to verify instrumentation is healthy, find instrumentation issues, or why evals or token/cost dashboards show n/a or zero. To debug app behavior or errors, use arize-trace.
metadata	{"author":"arize","version":"1.0"}
compatibility	Requires the ax CLI and a configured Arize profile. Analyzes exported OpenInference/OTel spans; language-agnostic.

Arize Instrumentation Health Skill

Use this skill for an on-demand instrumentation health audit over a project's existing traces — the aggregate counterpart to arize-instrumentation (which verifies a single new trace) and arize-trace (which exports and inspects spans). It answers questions like:

• "Why do my traces look empty or flat?"
• "Check whether my Arize instrumentation is healthy."
• "Find instrumentation issues in this project."
• "Why are my evals / token / cost dashboards showing n/a or zero?"

Workflow

1. Resolve scope — get the project (and space, if needed). If ambiguous, ask; do not guess.
2. Export a bounded span sample using the skill — do not hand-roll flags here. Follow its export guidance: start with a small sample scoped by to a recent window, into . Pull ~20 traces' worth of spans for a full audit (see minimum-data rules below).