phoenix-observability

Collect OpenTelemetry traces and run LLM evaluations in Phoenix.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/box755/simlens-research --skill phoenix-observability-box755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-observability
Source: https://github.com/box755/simlens-research/tree/main/skill-packs/AI-Research-SKILLs/17-observability/phoenix
Command: npx skills add https://github.com/box755/simlens-research --skill phoenix-observability-box755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires arize-phoenix>=12.0.0, arize-phoenix-otel, arize-phoenix-evals, openinference-instrumentation-openai, openinference-instrumentation-langchain, openinference-instrumentation-llama-index, openinference-instrumentation-anthropic, and includes references (resource) components.

What problem does it solve?

Phoenix observability solves the problem of debugging, evaluating, and monitoring LLM applications without visibility into what the model is doing across prompts, datasets, and production traffic.

Core Features & Use Cases

  • LLM tracing with OpenTelemetry: Capture detailed traces and spans for LLM calls across frameworks to pinpoint failures and latency hotspots.
  • Evaluation and quality scoring: Run LLM-as-judge evaluators on outputs, including hallucination, relevance, toxicity, and custom evaluation logic.
  • Datasets and experiments: Create versioned datasets and run repeatable experiments for prompt/model comparisons and regression testing.
  • Production monitoring and feedback logging: Query traces/spans, log user feedback/annotations, and export results for reporting.

Use Phoenix to debug a production chatbot by tracing missing/incorrect responses, run automated evaluation on a QA dataset before releasing prompt changes, and compare models or prompts using experiment runs and aggregate metrics.

Quick Start

Use the phoenix skill to trace OpenAI SDK calls in a running Phoenix server by installing arize-phoenix and registering OpenTelemetry with the correct traces endpoint, then viewing results in the Phoenix UI.

Frequently Asked Questions about phoenix-observability

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

FAQPage Schema
How do I trace LLM calls using OpenTelemetry for production observability?

LLM tracing with OpenTelemetry captures detailed traces and spans for LLM calls across frameworks to pinpoint failures and latency hotspots. You need to register OpenTelemetry with the correct traces endpoint in a running Phoenix server to collect this data.

Can I use LLM-as-judge evaluators to score model outputs for hallucination and toxicity?

LLM-as-judge evaluators score model outputs for hallucination, relevance, toxicity, and custom evaluation logic. These evaluation flows can log results back into Phoenix to monitor and assess output quality against defined criteria.

How do I run regression testing on LLM prompts using datasets and experiments?

Regression testing on LLM prompts uses versioned datasets and repeatable experiments to compare prompts and models. You can run batch workflows across notebooks and production services to compare aggregate metrics before releasing changes.

Does Phoenix observability work with LangChain and LlamaIndex for instrumentation?

Phoenix observability integrates with LangChain and LlamaIndex using openinference-instrumentation packages. It also supports OpenAI and Anthropic frameworks, requiring proper instrumentor integration to capture traces from these target LLM frameworks.

Do I need a Phoenix server setup to debug trace gaps in my LLM application?

A Phoenix server setup is required to debug trace gaps in your LLM application. You must install arize-phoenix, register OpenTelemetry with the correct traces endpoint, and integrate instrumentors for your target LLM frameworks to view results in the Phoenix UI.

What is the best way to monitor production chatbots and log user feedback?

Production monitoring and feedback logging queries traces and spans to debug missing or incorrect chatbot responses. You can log user feedback and annotations, then export results for reporting to maintain visibility into production traffic.