domino-experiment-tracking
Track traditional ML experiments in Domino's MLflow-based Experiment Manager. Covers unique experiment naming, auto-logging for scikit-learn, TensorFlow, PyTorch, XGBoost and LightGBM, manual logging of params, metrics and artifacts, Domino context tags, large-artifact multipart upload, comparing and exporting runs, and the Domino Model Registry (register from a run or by API, versions, aliases and tags, model cards, discoverability). Use when training ML models in Domino, logging metrics and parameters, comparing runs, or registering and versioning models. For GenAI tracing use domino-genai-tracing; to scaffold a helper module use domino-experiment-setup.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 5
- Forks
- 4
01 前言 Front Matter
- name
- domino-experiment-tracking
- description
- Track traditional ML experiments in Domino's MLflow-based Experiment Manager. Covers unique experiment naming, auto-logging for scikit-learn, TensorFlow, PyTorch, XGBoost and LightGBM, manual logging of params, metrics and artifacts, Domino context tags, large-artifact multipart upload, comparing and exporting runs, and the Domino Model Registry (register from a run or by API, versions, aliases and tags, model cards, discoverability). Use when training ML models in Domino, logging metrics and parameters, comparing runs, or registering and versioning models. For GenAI tracing use domino-genai-tracing; to scaffold a helper module use domino-experiment-setup.
- compatibility
- Domino 6.3 and Domino Cloud. Runs in a Domino Workspace or Job where MLFLOW_TRACKING_URI is preconfigured; registry REST routes need DOMINO_API_HOST with DOMINO_API_PROXY or the localhost:8899 access token in a run, a Personal Access Token outside.
02 资源文件 3
- 参考文档COMPARING-RUNS.md7.9 KB
- 参考文档MLFLOW-BASICS.md9.2 KB
- 参考文档MODEL-REGISTRY.md7.7 KB
03 SKILL.md 正文
Domino experiment tracking
Applies to Domino 6.3 and Domino Cloud.
Domino's Experiment Manager is MLflow Tracking with Domino's storage, access control and UI on top. In a Workspace or Job the mlflow package is installed (Domino Standard Environments) and MLFLOW_TRACKING_URI already points at Domino, so plain MLflow code works without configuration.
What is Domino-specific
- Experiments are created in code, not in the UI.
mlflow.set_experiment(name)creates it; it appears under Experiments only after the first run is logged. - Experiment names are unique across the whole deployment, not per project. Always suffix with something unique, for example the project and the user:
f"churn-{os.environ['DOMINO_PROJECT_NAME']}-{os.environ['DOMINO_STARTING_USERNAME']}". - Access follows the project: visibility (Private or Searchable; Domino 6.3 also has Public) and collaborator roles decide who sees runs. Results Consumers can view; Contributors and the owner can log and update; archiving another user's run needs the owner.
- Runs started from a Job are the reproducible ones (code commit, environment, hardware tier recorded). Workspace runs show the file name but are not re-versioned as you edit; finish in a Job.
- Give runs a
run_name; otherwise MLflow generates one likegifted-slug-123. - You cannot stop a run from the UI; call
mlflow.end_run()in the Workspace or Job. Deleting a parent run does not delete its children. - Compare up to four runs (select, Compare); export an experiment to CSV or a comparison to PDF from the three-dot menu.
- The Model Registry is Domino's (MLflow-backed, with model cards, role-based access and discoverability); R models are not supported.
Reference files
| File | Use when |
|---|---|
| MLFLOW-BASICS.md | Auto-logging, manual logging, artifacts, tags, nested runs |
| COMPARING-RUNS.md | Searching, comparing, exporting and loading runs programmatically |
| MODEL-REGISTRY.md | Registering, versioning with aliases and tags, model cards, registry REST routes |
Quick start
import os
import mlflow
from sklearn.ensemble import RandomForestClassifier
experiment = f"iris-{os.environ.get('DOMINO_PROJECT_NAME', 'local')}-{os.environ.get('DOMINO_STARTING_USERNAME', 'dev')}"
mlflow.set_experiment(experiment)
mlflow.autolog() # sklearn, tensorflow, pytorch, xgboost, lightgbm ...
with mlflow.start_run(run_name="rf-baseline"):
mlflow.set_tags({
"domino.project": os.environ.get("DOMINO_PROJECT_NAME", ""),
"domino.run_id": os.environ.get("DOMINO_RUN_ID", ""),
"domino.hardware_tier": os.environ.get("DOMINO_HARDWARE_TIER_ID", ""),
})
model = RandomForestClassifier(n_estimators=100).fit(X_train, y_train)
mlflow.log_metric("test_accuracy", model.score(X_test, y_test))
Framework auto-logging: mlflow.sklearn.autolog(), mlflow.tensorflow.autolog(), mlflow.pytorch.autolog(), mlflow.xgboost.autolog(), mlflow.lightgbm.autolog(), or mlflow.autolog() for all.
Domino variables worth tagging
| Variable | Value |
|---|---|
DOMINO_STARTING_USERNAME |
User who started the run |
DOMINO_PROJECT_NAME, DOMINO_PROJECT_OWNER, DOMINO_PROJECT_ID |
Project identity |
DOMINO_RUN_ID, DOMINO_RUN_NUMBER |
The Domino execution |
DOMINO_HARDWARE_TIER_ID |
Hardware tier id |
MLFLOW_TRACKING_URI |
Preconfigured; do not override |
Full list: https://docs.domino.ai/cloud/reference/environment-variables
Large artifacts
Multi-GB artifacts (LLM weights, checkpoints) upload straight to blob storage with MLFLOW_ENABLE_PROXY_MULTIPART_UPLOAD=true (AWS and GCP deployments): MLFLOW-BASICS.md.
Registering a model
From a run in the UI: Experiments > run > Register model from run. In code: mlflow.sklearn.log_model(model, "model", registered_model_name="churn-rf") or mlflow.register_model("runs:/<run_id>/model", "churn-rf"). Promote with aliases (client.set_registered_model_alias(name, "champion", version)), not the deprecated MLflow stages. Details, Domino registry routes (/api/registeredmodels/...), model cards and discoverability: MODEL-REGISTRY.md. To serve a registered version as an endpoint see domino-model-endpoints.
Documentation
04 同仓库更多 Skills
tags-and-properties
Manage Domino tags and properties via the Tags (Taxonomy) API at /api/taxonomy/v1. Covers namespaces and tags (create, list, update, deprecate, delete; tag entities such as projects, models, datasets, apps, project templates, NetApp volumes, environments; query by tag; autocomplete; merge; CSV import/export) and properties (typed metadata fields - text, number, date, boolean, url, user, organization, select, multi_select - with per-entity values, groups and versioned entities like model_version/app_version). Use when organizing entities with tags, building hierarchical namespaces, defining typed metadata fields, setting property values, finding entities by tag, bulk-tagging during onboarding, or migrating a taxonomy across environments.
netapp-volumes
Work with Domino Volumes for NetApp ONTAP (NetApp Volumes) - shared, multi-terabyte storage with near-instant snapshots. Covers creating volumes, attaching them to projects, mount paths (/mnt/netapp-volumes/ or /domino/netapp-volumes/), snapshots and tags, roles, deletion, mounting volumes in jobs, and the NetApp Volumes REST API (/remotefs/v1). Use when managing large-scale shared data, taking fast no-copy snapshots, or integrating NetApp ONTAP storage with Domino.
domino-workspaces
Work with Domino Workspaces - interactive sessions running Jupyter, JupyterLab, VS Code or RStudio on a hardware tier with a compute environment. Covers launching and configuring a Workspace, what persists across stop and resume, file paths and syncing for DFS and Git-based Projects, package and home-directory persistence, SSH access from a local IDE, the Workspace API routes, and troubleshooting. Use when setting up or debugging an interactive development session in Domino.
domino-ui-bootstrap
Bootstrap or retrofit a Vite + React 18 + TypeScript project so it uses the Domino design system (`@dominodatalab/extensions-tools`). Scoped to a **fully standalone SPA frontend for a Domino application or extension**, not snippets, library additions, or work inside an existing Domino monorepo package. Use whenever the user wants to create, scaffold, refactor, retrofit, or set up such an SPA (a React app, web app, frontend, UI, or extension) that should "look like Domino", use Domino components, follow the Domino design system, or integrate with the Domino platform, including when they mention DominoThemeProviderDecorator, extensions-tools, or base-components without saying "Domino". Also use to make an existing standalone React/Vite project "Domino-styled" or add Domino theming. Handles React 18 / react-router 5 pinning, Storybook MCP registration, theme provider wiring, and build verification.
domino-trace-setup
Set up GenAI tracing for an LLM or agent application in Domino by checking the Domino SDK and MLflow requirements (the DSE needs nothing installed), then adding a tracing_setup.py helper, span evaluators, a config.yaml, and @add_tracing / DominoAgentContext wiring. Use when the user asks to add tracing, observability, or evaluation to an agent or LLM app running on Domino.
domino-rust-apps
Build a Rust web app (axum) in Domino and ship it as a Domino App that starts from a prebuilt binary. Covers installing a pinned Rust toolchain into a Compute Environment with rustup, Cargo project defaults (edition 2024, rust-toolchain.toml, Cargo.lock, Clippy pedantic, rustfmt, cargo-nextest, cargo-deny), rust-analyzer for the IDE and coding agents, check hooks, calling Domino as the viewer with extended identity propagation, dev and release build profiles, keeping target/ out of Git and Domino storage, and an app.sh that runs the binary in App Preview and deployments without compiling. Use when the user wants a Rust app, API, dashboard or Proa site on Domino, a performance-sensitive or correctness-critical App, or asks to set up Rust, cargo, Clippy, nextest or rust-analyzer in a Domino Workspace or environment.