retrieving-mlflow-traces

Retrieve MLflow traces by ID or search criteria with filtering and pagination.

Updated Sep 9, 2017
One-click install
npx skills add https://github.com/mirakui/dotfiles --skill retrieving-mlflow-traces-mirakui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrieving-mlflow-traces
Source: https://github.com/mirakui/dotfiles/tree/main/claude/skills/retrieving-mlflow-traces
Command: npx skills add https://github.com/mirakui/dotfiles --skill retrieving-mlflow-traces-mirakui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve and inspect MLflow traces efficiently, enabling rapid debugging and monitoring across experiments and runs without manual log hunting.

Core Features & Use Cases

  • Fetch a single trace by trace-id for quick diagnostics.
  • Search traces by run, experiment, session, user, status, time range, or metadata.
  • Debug failed traces and compare traces to identify root causes.
  • Export or view trace details and spans for deeper analysis.

Quick Start

Ask me to fetch a trace by ID or search for traces with criteria such as experiment-id or status.

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 a specific experiment run?

You can retrieve MLflow traces by searching with experiment-id, run-id, session, or user criteria via the MLflow Python API or CLI, applying filter syntax to narrow down the exact traces needed.

How do I filter MLflow traces by status and time range?

Filter MLflow traces by status, time range, tags, and metadata using supported filter syntax within the MLflow Python API or CLI to isolate specific execution records for monitoring.

Can I fetch a single MLflow trace by its trace ID for debugging?

Yes, you can fetch a single trace directly by its trace-id using the MLflow Python API or CLI, enabling quick diagnostics and inspection of trace details and spans for root cause analysis.

Does MLflow trace retrieval support pagination for large experiments?

Yes, MLflow trace retrieval supports pagination and detailed trace output, enabling management and inspection of large volumes of trace data across extensive ML experiments without manual log hunting.

What is the best way to search and compare failed MLflow traces?

The best way to compare failed MLflow traces is to search by status and metadata using filter syntax, then export or view trace details and spans to identify root causes across runs.

Why am I unable to find specific MLflow traces during experiment auditing?

If you cannot find specific MLflow traces, ensure you are using the correct filter syntax for status, time, tags, or metadata, and verify you are querying the right experiment or run ID via the Python API.