Litellm OpenTelemetry Integration
Overview
This integration provides support for using OpenTelemetry with the Litellm framework. It enables tracing and monitoring of applications built with Litellm.
Installation
- Install traceAI Litellm
pip install traceAI-litellm tenacity
Set Environment Variables
Set up your environment variables to authenticate with FutureAGI
import os
os.environ["FI_API_KEY"] = FI_API_KEY
os.environ["FI_SECRET_KEY"] = FI_SECRET_KEY
Quickstart
Register Tracer Provider
Set up the trace provider to establish the observability pipeline. The trace provider:
from fi_instrumentation import register
from fi_instrumentation.fi_types import ProjectType
trace_provider = register(
project_type=ProjectType.OBSERVE,
project_name="litellm_app"
)
Configure Litellm Instrumentation
Instrument the Litellm client to enable telemetry collection. This step ensures that all interactions with the Litellm SDK are tracked and monitored.
from traceai_litellm import LiteLLMInstrumentor
LiteLLMInstrumentor().instrument(tracer_provider=trace_provider)
Create Litellm Components
Set up your Litellm client with built-in observability.
import asyncio
import litellm
async def run_examples():
# Simple single message completion call
litellm.completion(
model="gpt-3.5-turbo",
messages=[{"content": "What's the capital of China?", "role": "user"}],
)
# Multiple message conversation completion call with added param
litellm.completion(
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,
)
# Multiple message conversation acompletion call with added params
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,
)
# Completion with retries
litellm.completion_with_retries(
model="gpt-3.5-turbo",
messages=[{"content": "What's the highest grossing film ever", "role": "user"}],
)
# Embedding call
litellm.embedding(
model="text-embedding-ada-002", input=["good morning from litellm"]
)
# Asynchronous embedding call
await litellm.aembedding(
model="text-embedding-ada-002", input=["good morning from litellm"]
)
# Image generation call
litellm.image_generation(model="dall-e-2", prompt="cute baby otter")
# Asynchronous image generation call
await litellm.aimage_generation(model="dall-e-2", prompt="cute baby otter")
asyncio.run(run_examples())
Metadata
Release files for traceAI-litellm 0.1.12
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 | Actions |
|---|---|---|---|---|
| traceai_litellm-0.1.12.tar.gz | 10.0 kB | With provenance | Details for traceai_litellm-0.1.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| traceai_litellm-0.1.12-py3-none-any.whl | Python 3 | none | any | Details for traceai_litellm-0.1.12-py3-none-any.whl |
Total release size: 19.8 kB
Release files / traceai_litellm-0.1.12.tar.gz
| Download URL | traceai_litellm-0.1.12.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1116951a2379edaa51a1f1b8057247e698fe2cc5632566d218f34fd09feef69d
|
|
BLAKE2b-256 checksum How to use checksums |
c23de7342d0f0fce7448350d6e3437aafee7d5dc1b7bcf470d488f46100514b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logRelease files / traceai_litellm-0.1.12-py3-none-any.whl
| Download URL | traceai_litellm-0.1.12-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ace563479386860c6ae140939edf20b16ccf512c5ee7ba869a0ae2e3df21ca4
|
|
BLAKE2b-256 checksum How to use checksums |
4188ad0f21fa5ef4eb4c801e9da1911999fd14a921d81407cdd609b65744a91a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logSecurity for traceAI-litellm 0.1.12
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
Both files in this release have been uploaded with provenance metadata.
Attestation for traceai_litellm-0.1.12.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 Nov 12, 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.