Arize Span Routing Skill

Use this skill to send each traced operation from one Python service to its correct Arize space and project. Each operation must resolve to exactly one space_id and project_name before its first span starts.

Do not use this skill for ordinary single-project tracing; use arize-instrumentation. This skill does not reroute spans after export, backfill historical spans, create Arize spaces/projects, or invent a customer-specific metadata mapping.

Safety rules

• Never guess a destination or silently use another tenant's destination.
• Never embed API keys in code or ask users to paste keys into chat. Read ARIZE_API_KEY from the environment.
• Preserve existing non-Arize exporters and processors. Remove or replace a fixed-destination Arize export path so routed spans are not also copied to that destination.
• Missing, invalid, or unavailable routing metadata must leave the business operation running but its spans unexported to Arize. Run that operation under a fresh OpenTelemetry context so stale routing values cannot leak across tenants. Log a warning without including secrets or sensitive metadata values.
• Use one API key that is authorized for every destination space. Stop and report a credential blocker if that is not true.

Phase 1: Inspect and define the contract

Read only until the routing contract is clear.