retrieving-mlflow-traces

Retrieve MLflow traces by ID or filter by run, session, and time.

4|2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/alessandro9110/Speech-To-Text-With-Databricks --skill retrieving-mlflow-traces-alessandro9110
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrieving-mlflow-traces
Source: https://github.com/alessandro9110/Speech-To-Text-With-Databricks/tree/main/.claude/skills/retrieving-mlflow-traces
Command: npx skills add https://github.com/alessandro9110/Speech-To-Text-With-Databricks --skill retrieving-mlflow-traces-alessandro9110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you find and retrieve specific MLflow traces, especially when debugging or analyzing performance issues, by allowing you to search and filter traces based on various criteria.

Core Features & Use Cases

  • Trace Retrieval: Get details of a single trace using its ID.
  • Trace Searching: Find traces by run ID, session, user, status, time range, tags, metadata, or execution time.
  • Debugging: Quickly identify failed traces within a specific session or user context.
  • Performance Analysis: Filter traces that exceed a certain execution time to pinpoint performance bottlenecks.

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 search for failed MLflow traces in a specific experiment?

To search for failed MLflow traces, filter by status and experiment ID. This skill allows you to query traces by run ID, session, user, tags, metadata, execution time, and status to quickly identify and debug failed runs.

Can I filter MLflow traces by execution time for performance analysis?

Yes, you can filter MLflow traces by execution time for performance analysis. This allows you to pinpoint performance bottlenecks by querying and retrieving only the traces that exceed a specified execution time threshold.

What is the best way to retrieve a specific MLflow trace by its ID?

The best way to retrieve a specific MLflow trace by its ID is using the MLflow CLI or Python API. This skill directly fetches the complete details of a single trace when provided with its unique identifier.

How do I query MLflow traces using tags and metadata?

You can query MLflow traces by filtering on tags and metadata. The skill supports searching traces based on custom tags, metadata, run ID, session, user, status, and time ranges to find exact matching records.

Does this MLflow trace retrieval skill support filtering by time ranges?

Yes, this MLflow trace retrieval skill supports filtering by time ranges. You can search for traces within specific time periods alongside filtering by run ID, session, user, status, tags, metadata, and execution time.