Skip to content

Manual import script should emit mlflow_run_id and mlflow_experiment_id columns #107

Open

Description

@aas008

Summary

The manual import script (manual_runs/scripts/vllm/import_manual_runs_json_v2.py) does not emit mlflow_run_id or mlflow_experiment_id columns. These were added to the dashboard CSV schema in PR #83 to render clickable MLflow artifact links in the Filtered Data table.

When a manually-imported CSV is appended to the consolidated S3 CSV, rows imported via the script have empty values for these two columns and therefore show no MLflow link in the Filtered Data table — even though the source data came from a known MLflow run.

Current behaviour

Expected behaviour

The import script should accept --mlflow-run-id and --mlflow-experiment-id CLI flags (both optional, default to empty) and include them in the output CSV. When a user imports a run they fetched from MLflow, they can pass the run ID so the dashboard shows a working MLflow link.

Proposed fix

Add two optional CLI arguments:

--mlflow-run-id       MLflow run UUID (32-char hex), e.g. c6aa48a0d312448380621e1bf00a8a5d
--mlflow-experiment-id  MLflow experiment ID, e.g. 264

Include them in the fieldnames list and populate the row dict accordingly.

Context

Activity

  1. added 2 commits that reference this issue on Oct 7, 2026
    f56017f
    7f10ef6
  2. added 2 commits that reference this issue on Oct 15, 2026
    b39d1cf
    a424aa0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions