MLflow Tracing: An Open-Source SDK for Observability and Monitoring GenAI Applications🔍
MLflow Tracing (mlflow-tracing) is an open-source, lightweight Python package that only includes the minimum set of dependencies and functionality
to instrument your code/models/agents with MLflow Tracing Feature. It is designed to be a perfect fit for production environments where you want:
- ⚡️ Faster Deployment: The package size and dependencies are significantly smaller than the full MLflow package, allowing for faster deployment times in dynamic environments such as Docker containers, serverless functions, and cloud-based applications.
- 🔧 Simplified Dependency Management: A smaller set of dependencies means less work keeping up with dependency updates, security patches, and breaking changes from upstream libraries.
- 📦 Portability: With the less number of dependencies, MLflow Tracing can be easily deployed across different environments and platforms, without worrying about compatibility issues.
- 🔒 Fewer Security Risks: Each dependency potentially introduces security vulnerabilities. By reducing the number of dependencies, MLflow Tracing minimizes the attack surface and reduces the risk of security breaches.
✨ Features
- Automatic Tracing for AI libraries (OpenAI, LangChain, DSPy, Anthropic, etc...). Follow the link for the full list of supported libraries.
- Manual instrumentation APIs such as
@tracedecorator. - Production Monitoring
- Other tracing APIs such as
mlflow.set_trace_tag,mlflow.search_traces, etc.
🌐 Choose Backend
The MLflow Trace package is designed to work with a remote hosted MLflow server as a backend. This allows you to log your traces to a central location, making it easier to manage and analyze your traces. There are several different options for hosting your MLflow server, including:
- Databricks - Databricks offers a FREE, fully managed MLflow server as a part of their platform. This is the easiest way to get started with MLflow tracing, without having to set up any infrastructure.
- Amazon SageMaker - MLflow on Amazon SageMaker is a fully managed service offered as part of the SageMaker platform by AWS, including tracing and other MLflow features such as model registry.
- Nebius - Nebius, a cutting-edge cloud platform for GenAI explorers, offers a fully managed MLflow server.
- Self-hosting - MLflow is a fully open-source project, allowing you to self-host your own MLflow server and keep your data private. This is a great option if you want to have full control over your data and infrastructure.
🚀 Getting Started
Installation
To install the MLflow Python package, run the following command:
pip install mlflow-tracing
To install from the source code, run the following command:
pip install git+https://github.com/mlflow/mlflow.git#subdirectory=libs/tracing
NOTE: It is not recommended to co-install this package with the full MLflow package together, as it may cause version mismatches issues.
Connect to the MLflow Server
To connect to your MLflow server to log your traces, set the MLFLOW_TRACKING_URI environment variable or use the mlflow.set_tracking_uri function:
import mlflow
mlflow.set_tracking_uri("databricks")
# Specify the experiment to log the traces to
mlflow.set_experiment("/Path/To/Experiment")
Start Logging Traces
import openai
client = openai.OpenAI(api_key="<your-api-key>")
# Enable auto-tracing for OpenAI
mlflow.openai.autolog()
# Call the OpenAI API as usual
response = client.chat.completions.create(
model="gpt-4.1-mini",
messages=[{"role": "user", "content": "Hello, how are you?"}],
)
📘 Documentation
Official documentation for MLflow Tracing can be found at here.
🛑 Features Not Included
The following MLflow features are not included in this package.
- MLflow tracking server and UI.
- MLflow's other tracking capabilities such as Runs, Model Registry, Projects, etc.
- Evaluate models/agents and log evaluation results.
To leverage the full feature set of MLflow, install the full package by running pip install mlflow.
Metadata
Release files for mlflow-tracing 3.16.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mlflow_tracing-3.16.1.tar.gz | 1.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlflow_tracing-3.16.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / mlflow_tracing-3.16.1.tar.gz
| Download URL | mlflow_tracing-3.16.1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
315ba1ace00d43498da2ad2b2bbb751f3198d6f9cd328168dfeb49911df41925
|
|
BLAKE2b-256 checksum How to use checksums |
886264068c0d17a7ba479f4dadfa78b3e48921cde8d20878414e7a4a929e66c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 16, 2026.
Transparency logRelease files / mlflow_tracing-3.16.1-py3-none-any.whl
| Download URL | mlflow_tracing-3.16.1-py3-none-any.whl |
|---|---|
| Size | 1.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3ab97c7b4f919704e0cbe0653e6e9b89cf1f8a790f8bb1b4cf7f236df258e9e
|
|
BLAKE2b-256 checksum How to use checksums |
008cf40c01433254f49f3b18ef88a4eba481a73a29494f27c072fb7a53812a76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 16, 2026.
Transparency log