retrieving-mlflow-traces

Retrieve MLflow traces by ID or search with filters via CLI or Python API.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/slysik/databricks-claude-coding --skill retrieving-mlflow-traces-slysik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrieving-mlflow-traces
Source: https://github.com/slysik/databricks-claude-coding/tree/main/.agents/skills/retrieving-mlflow-traces
Command: npx skills add https://github.com/slysik/databricks-claude-coding --skill retrieving-mlflow-traces-slysik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of retrieving and analyzing MLflow traces, making it easier to debug failed runs, understand performance, and find specific trace data.

Core Features & Use Cases

  • Trace Retrieval: Fetch individual traces by ID or search for traces based on various criteria.
  • Filtering: Filter traces by status, session, user, tags, metadata, execution time, and more.
  • Debugging: Quickly identify and investigate failed traces within specific sessions or experiments.
  • Use Case: When a user reports an issue with a specific session, use this Skill to find all traces from that session, especially any that failed, to diagnose the root cause.

Quick Start

Use the retrieving-mlflow-traces skill to search for failed traces in experiment ID 1.

Frequently Asked Questions about retrieving-mlflow-traces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve MLflow traces for debugging failed runs?

Retrieve MLflow traces by fetching individual records by ID or searching with complex filters to debug failed runs and understand execution performance.

Can I search MLflow traces using complex filters?

Search MLflow traces using complex filters based on status, metadata, tags, and execution time, and paginate results to find specific data.

How do I find failed MLflow traces within a specific session?

Find failed MLflow traces within specific sessions by filtering on session ID and status to diagnose the root cause of reported issues.

Does retrieving MLflow traces work with both CLI and Python API?

Retrieving MLflow traces works using CLI commands or the Python API, allowing you to fetch data by ID, search with filters, and paginate results.

What is the best way to monitor ML experiment execution time using traces?

Monitor ML experiment execution time by searching MLflow traces with filters applied to execution time metrics to analyze performance bottlenecks.

Why do I need to paginate MLflow trace search results?

Paginate MLflow trace search results to manage large datasets returned from complex filters based on status, tags, and metadata during debugging.