Skip to main content

Overview

MLflow is an open-source platform for managing the end-to-end machine learning and AI lifecycle. MLflow Tracing provides detailed observability into AI agent execution, capturing LLM calls, tool usage, and agent decisions with a rich visualization UI. Since Pipecat’s built-in tracing uses OpenTelemetry, you can send traces directly to MLflow’s OTLP endpoint for visualization and analysis.

MLflow Tracing Docs

Learn about MLflow’s tracing capabilities

MLflow Pipecat Integration

MLflow’s guide for tracing Pipecat applications

MLflow GitHub

Browse the MLflow open-source repository

MLflow Platform

Explore the MLflow platform

Installation

Install Pipecat with tracing support and the OTLP HTTP exporter:

Prerequisites

Start MLflow

The quickest way to start the MLflow tracking server is with uvx (no installation needed):
The MLflow UI will be available at http://localhost:5000.
For other setup options including Docker and pip, see the MLflow environment setup guide.If you prefer a managed solution, Managed MLflow on AWS SageMaker or Databricks provides a fully hosted MLflow experience with no infrastructure to manage.

Key Features

  • Trace visualization: Inspect every LLM call, STT/TTS operation, and conversation turn in a hierarchical trace view
  • Token usage tracking: Monitor input/output token counts across conversations
  • Performance metrics: Track TTFB, processing duration, and latency for each service
  • Evaluation framework: Evaluate agent outputs using built-in LLM judges and custom scorers
  • Open source: Fully open-source with no vendor lock-in, self-host anywhere

Configuration

Configure the OTLP HTTP exporter to send traces to MLflow:
Alternatively, configure with environment variables:
The x-mlflow-experiment-id header specifies which MLflow experiment to log traces to. Use 0 for the default experiment, or create a dedicated experiment:

Usage

Basic Setup

After running your Pipecat application, open the MLflow UI at http://localhost:5000 and navigate to the Traces tab to see detailed traces of your voice agent conversations, including STT, LLM, and TTS spans with latency and token usage. Pipecat traces in MLflow

Troubleshooting

  • No traces visible: Verify the MLflow server is running and the OTEL_EXPORTER_OTLP_ENDPOINT points to the correct address
  • Missing service data: Ensure enable_metrics=True is set in PipelineParams
  • Connection errors: Check that the MLflow server is accessible from your application and the endpoint URL is correct
  • Wrong experiment: Set the x-mlflow-experiment-id header to direct traces to the correct experiment

References