Arize Phoenix

Arize Phoenix is documented as an open-source AI observability and evaluation platform built on OpenTelemetry and OpenInference. Its documented surface includes traces for model calls, retrieval, tool use and custom logic, together with evaluation, versioned datasets and experiments. Phoenix OSS and the managed Arize AX workflow are separate operational and contractual boundaries.

Phoenix documentation describes OpenTelemetry/OpenInference-based instrumentation and OTLP ingestion for AI application tracing. Documentation and repository availability establish capabilities, not complete instrumentation, secure deployment, evaluator validity, or enterprise SLO.

Phoenix can be used as a locally controlled observability/evaluation layer, but an OSS label, OpenTelemetry support, integration listing, or visible trace is not proof of complete visibility, privacy-safe capture, correct evaluation, production readiness, or parity with Arize AX.

Pin and verify the Phoenix release/commit and package versions, Phoenix OSS versus Arize AX boundary, ELv2 obligations, OTLP collector/exporter/backend, supported framework/provider/language, auto/manual instrumentation, sampling and redaction, authentication/RBAC/tenant controls, storage/backup/retention/region, dataset/evaluator versions, deployment/upgrade path, cost and SLO.

Evidence-only desk research. No Phoenix server, UI, SDK, OTLP exporter, evaluation, dataset, or Arize AX tenant was exercised by the source packet.

Current component releases; exact ELv2 scope for the intended use; instrumentation matrix; OpenTelemetry/OpenInference parity; trace loss and overhead; evaluator behavior; self-host security defaults; managed feature, region, retention and SLO behavior; public incident completeness.

Traces can contain prompts, outputs, retrievals, tool calls and identities. Redaction and access controls must be applied before export; collector, backend, UI and backups require protection. Self-hosting transfers compute, storage, backup, upgrade, patching and incident-response obligations to the deployer.

Do not treat Phoenix's OSS label, OpenTelemetry foundation, integration list, or UI trace as proof of complete observability, safe privacy, correct evaluation, or Arize AX equivalence.