All skills
github avatar

/phoenix-tracing

@4214189 official
by githubgithub/awesome-copilot40k stars
5,040

OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/phoenix-tracing

This session only. Nothing lands on disk.

referencesfundamentals-required-attributes.md

≈621 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Required and Recommended Attributes

This document covers the required attribute and highly recommended attributes for all OpenInference spans.

Required Attribute

Every span MUST have exactly one required attribute:

{
  "openinference.span.kind": "LLM"
}

Highly Recommended Attributes

While not strictly required, these attributes are highly recommended on all spans as they:

  • Enable evaluation and quality assessment
  • Help understand information flow through your application
  • Make traces more useful for debugging

Input/Output Values

Attribute Type Description
input.value String Input to the operation (prompt, query, document)
output.value String Output from the operation (response, result, answer)

Example:

{
  "openinference.span.kind": "LLM",
  "input.value": "What is the capital of France?",
  "output.value": "The capital of France is Paris."
}

Why these matter:

  • Evaluations: Many evaluators (faithfulness, relevance, hallucination detection) require both input and output to assess quality
  • Information flow: Seeing inputs/outputs makes it easy to trace how data transforms through your application
  • Debugging: When something goes wrong, having the actual input/output makes root cause analysis much faster
  • Analytics: Enables pattern analysis across similar inputs or outputs

Phoenix Behavior:

  • Input/output displayed prominently in span details
  • Evaluators can automatically access these values
  • Search/filter traces by input or output content
  • Export inputs/outputs for fine-tuning datasets

Valid Span Kinds

There are exactly 9 valid span kinds in OpenInference:

Span Kind Purpose Common Use Case
LLM Language model inference OpenAI, Anthropic, local LLM calls
EMBEDDING Vector generation Text-to-vector conversion
CHAIN Application flow orchestration LangChain chains, custom workflows
RETRIEVER Document/context retrieval Vector DB queries, semantic search
RERANKER Result reordering Rerank retrieved documents
TOOL External tool invocation API calls, function execution
AGENT Autonomous reasoning ReAct agents, planning loops
GUARDRAIL Safety/policy checks Content moderation, PII detection
EVALUATOR Quality assessment Answer relevance, faithfulness scoring

Source: SKILL.md on GitHub

No alerts9d4 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    The phoenix-tracing skill provides comprehensive documentation and implementation guides for instrumenting LLM applications with Phoenix and OpenInference semantic conventions. It covers setup, manual and auto-instrumentation, and production best practices for both Python and TypeScript, with a strong focus on secure data handling and PII masking.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4214189. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
Other metadata
compatibility
Requires Phoenix server. Python skills need arize-phoenix-otel; TypeScript skills need @arizeai/phoenix-otel.
metadata
{
  "author": "oss@arize.com",
  "version": "1.0.0",
  "languages": "Python, TypeScript"
}
  • Python
  • TypeScript
  • phoenix
  • tracing
  • openinference
  • llm-observability
  • instrumentation
  • otel
  • arize

README badge

README badge for github/awesome-copilot/phoenix-tracing

Instruments LLM applications with OpenInference tracing in Phoenix, supporting auto-instrumentation of frameworks like OpenAI and LangChain or custom manual spans. Covers setup, span types (LLM calls, retrievers, agents, evaluators), production deployment with PII masking, and feedback annotation in Python and TypeScript.

Generated from the current SKILL.md.

Does this skill work with both Python and TypeScript?
Yes. The skill provides separate setup, instrumentation, and production guides for both Python (arize-phoenix-otel) and TypeScript (@arizeai/phoenix-otel).
What do I need to install to use this skill?
For Python: arize-phoenix-otel package. For TypeScript: @arizeai/phoenix-otel package. Both require a running Phoenix server endpoint.
Can I auto-instrument frameworks like OpenAI or LangChain?
Yes. The skill includes instrumentation-auto-{lang} references that cover auto-instrumentation for supported frameworks in both languages.
How do I track custom spans for my own operations?
Use the instrumentation-manual-{lang} references to create custom spans with decorators (Python) or wrappers (TypeScript), then refer to span-{type} files for the appropriate attribute schema.
Does this skill cover production deployment concerns?
Yes. The production-{lang} references address batch processing, PII masking, and deployment patterns for production environments.

Generated from the current SKILL.md. These answers refresh after source changes.