OpenInference Pipecat Instrumentation
Python auto-instrumentation library for Pipecat. This library allows you to convert Pipecat traces to OpenInference, which is OpenTelemetry compatible, and view those traces in Arize Phoenix or Arize AX.
Compatibility
openinference-instrumentation-pipecat |
pipecat-ai |
Python |
|---|---|---|
>=2.0 |
>=1.3 |
>=3.11 |
>=1.0, <2.0 |
>=1.0, <1.3 |
>=3.11 |
<=0.1.4 |
<1.0 (e.g. 0.0.99) |
>=3.10 |
Pipecat 1.3 deprecated PipelineTask in favor of PipelineWorker. Instrumentor
versions <2.0 only wrap PipelineTask, so bots built on PipelineWorker get
no observer injection and emit no spans. Use >=2.0 with pipecat-ai>=1.3.
Pipecat 1.0 introduced breaking changes (renamed observers, removed
LLMMessagesFrame, dropped Python 3.10). If you're still on pipecat-ai<1.0,
pin this instrumentor to <=0.1.4:
pip install 'openinference-instrumentation-pipecat<=0.1.4' 'pipecat-ai<1.0'
Installation
pip install openinference-instrumentation-pipecat
Quickstart
This quickstart shows you how to setup tracing in your Pipecat application:
from phoenix.otel import register
from openinference.instrumentation.pipecat import PipecatInstrumentor
# Set up the tracer provider
tracer_provider = register(
project_name="default" #Phoenix project name
)
# Add auto-instrumentor at the top of the application
PipecatInstrumentor().instrument(tracer_provider=tracer_provider)
# Build your Pipecat pipeline
# ... (add your Pipecat pipeline code here)
### CONFIGURATION SETUP (Transport, LLM, STT, TTS) ###
### PIPELINE ###
pipeline = Pipeline(...)
### WORKER ###
worker = PipelineWorker(
pipeline,
conversation_id=conversation_id, # conversation id is used for session tracking in Arize or Phoenix
)
### EVENT HANDLING
@transport.event_handler("on_client_connected")
async def on_client_connected(transport, client):
await worker.queue_frames([LLMRunFrame()])
### PIPELINE RUNNER ###
runner = PipelineRunner(handle_sigint=runner_args.handle_sigint)
await runner.run(worker)
After configuring tracing, exchanges in the running application are logged to your project in Phoenix or Arize AX.
Example
- Install dependencies
uv pip install -e '.[examples]'
or
uv pip install -r examples/trace/requirements.txt
- Run example
uv run python examples/trace/001-trace.py
More Info
1 maintainer
Metadata
1 maintainer
Release files for openinference-instrumentation-pipecat 2.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openinference_instrumentation_pipecat-2.0.4.tar.gz | 33.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openinference_instrumentation_pipecat-2.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.1 kB
Release files / openinference_instrumentation_pipecat-2.0.4.tar.gz
| Download URL | openinference_instrumentation_pipecat-2.0.4.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e4643e5149a8b6bd6bf8c1c15e54d6a178321c899644a1e2140eaa970930455
|
|
BLAKE2b-256 checksum How to use checksums |
6dc83f335d265d40cf188f97be7c20b1f8592099db97f09a6eb8e0ea6f851c27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logRelease files / openinference_instrumentation_pipecat-2.0.4-py3-none-any.whl
| Download URL | openinference_instrumentation_pipecat-2.0.4-py3-none-any.whl |
|---|---|
| Size | 24.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d62a6a9137ad9f11ab17de0f0c7982587034358872aba16878a6cb1e3cbfe6fd
|
|
BLAKE2b-256 checksum How to use checksums |
2a9a07f61fb221b62d78ffd328276aed42c31c6e07fd5606a8b8dd0bf69a138c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logSecurity for openinference-instrumentation-pipecat 2.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for openinference_instrumentation_pipecat-2.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
