OpenInference LiteLLM Instrumentation
LiteLLM allows developers to call all LLM APIs using the openAI format. LiteLLM Proxy is a proxy server to call 100+ LLMs in OpenAI format. Both are supported by this auto-instrumentation.
This package implements OpenInference tracing for the following LiteLLM functions:
- completion()
- acompletion()
- completion_with_retries()
- embedding()
- aembedding()
- image_generation()
- aimage_generation()
- anthropic.messages.create()
- anthropic.messages.acreate()
These traces are fully OpenTelemetry compatible and can be sent to an OpenTelemetry collector for viewing, such as Arize Phoenix or Arize AX.
Installation
pip install openinference-instrumentation-litellm
Quickstart
In a notebook environment (jupyter, colab, etc.) install openinference-instrumentation-litellm if you haven't already as well as arize-phoenix and litellm.
pip install openinference-instrumentation-litellm arize-phoenix litellm
First, import dependencies required to autoinstrument liteLLM and set up phoenix as an collector for OpenInference traces.
import litellm
import phoenix as px
from openinference.instrumentation.litellm import LiteLLMInstrumentor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
Next, we'll start a phoenix server and set it as a collector.
session = px.launch_app()
endpoint = "http://127.0.0.1:6006/v1/traces"
tracer_provider = TracerProvider()
tracer_provider.add_span_processor(SimpleSpanProcessor(OTLPSpanExporter(endpoint)))
Set up any API keys needed in you API calls. For example:
import os
os.environ["OPENAI_API_KEY"] = "PASTE_YOUR_API_KEY_HERE"
Instrumenting LiteLLM is simple:
LiteLLMInstrumentor().instrument(tracer_provider=tracer_provider)
Now, all calls to LiteLLM functions are instrumented and can be viewed in the phoenix UI.
completion_response = litellm.completion(model="gpt-3.5-turbo",
messages=[{"content": "What's the capital of China?", "role": "user"}])
print(completion_response)
acompletion_response = await litellm.acompletion(
model="gpt-3.5-turbo",
messages=[{ "content": "Hello, I want to bake a cake","role": "user"},
{ "content": "Hello, I can pull up some recipes for cakes.","role": "assistant"},
{ "content": "No actually I want to make a pie","role": "user"},],
temperature=0.7,
max_tokens=20
)
print(acompletion_response)
embedding_response = litellm.embedding(model='text-embedding-ada-002', input=["good morning!"])
print(embedding_response)
image_gen_response = litellm.image_generation(model='dall-e-2', prompt="cute baby otter")
print(image_gen_response)
You can also uninstrument the functions as follows
LiteLLMInstrumentor().uninstrument(tracer_provider=tracer_provider)
Now any liteLLM function calls you make will not send traces to Phoenix until instrumented again
More Info
1 maintainer
Metadata
1 maintainer
Release files for openinference-instrumentation-litellm 0.1.51
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_litellm-0.1.51.tar.gz | 119.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openinference_instrumentation_litellm-0.1.51-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 145.9 kB
Release files / openinference_instrumentation_litellm-0.1.51.tar.gz
| Download URL | openinference_instrumentation_litellm-0.1.51.tar.gz |
|---|---|
| Size | 119.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe05b97aede7658a8c9ef88842770fbae66590a27826bc20c12fa15f0a4a868d
|
|
BLAKE2b-256 checksum How to use checksums |
3a6bde2d595180af3a3201587cd60883a75b0db311c0d6332ca6b5c04aff2680
|
| 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 Oct 23, 2026.
Transparency logRelease files / openinference_instrumentation_litellm-0.1.51-py3-none-any.whl
| Download URL | openinference_instrumentation_litellm-0.1.51-py3-none-any.whl |
|---|---|
| Size | 26.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d4d90cbbf059c57fd7ff7d636c61b88ed8729b3a61ef70198027690a5a5d45b
|
|
BLAKE2b-256 checksum How to use checksums |
675b894cd83e903ec44244ed7184198a161824678d074e2510cedf0cd2818d40
|
| 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 Oct 23, 2026.
Transparency logSecurity for openinference-instrumentation-litellm 0.1.51
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_litellm-0.1.51.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 Oct 23, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
