Skip to content

Commit 6db1df0

Browse files
authored
Merge pull request #495 from v-thepet/mlflow-cli
Freshness 5 - 180 days freshness updates
2 parents 003e553 + 3d47716 commit 6db1df0

File tree

4 files changed

+106
-115
lines changed

4 files changed

+106
-115
lines changed

articles/machine-learning/concept-mlflow.md

Lines changed: 28 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: mopeakande
88
ms.reviewer: cacrest
99
ms.service: azure-machine-learning
1010
ms.subservice: mlops
11-
ms.date: 09/25/2024
11+
ms.date: 09/30/2024
1212
ms.topic: concept-article
1313
ms.custom: cliv2, sdkv2, FY25Q1-Linter
1414
#Customer intent: As a data scientist, I want to understand what MLflow is and does so that I can use MLflow with my models.
@@ -29,11 +29,37 @@ Azure Machine Learning workspaces are MLflow-compatible, which means that you ca
2929
> [!TIP]
3030
> Unlike the Azure Machine Learning SDK v1, there's no logging functionality in the Azure Machine Learning v2 SDK. You can use MLflow logging to ensure that your training routines are cloud-agnostic, portable, and have no dependency on Azure Machine Learning.
3131
32+
## What is tracking
33+
34+
When you work with jobs, Azure Machine Learning automatically tracks some information about experiments, such as code, environment, and input and output data. However, models, parameters, and metrics are specific to the scenario, so model builders must configure their tracking.
35+
36+
The saved tracking metadata varies by experiment, and can include:
37+
38+
- Code
39+
- Environment details such as OS version and Python packages
40+
- Input data
41+
- Parameter configurations
42+
- Models
43+
- Evaluation metrics
44+
- Evaluation visualizations such as confusion matrices and importance plots
45+
- Evaluation results, including some evaluation predictions
46+
47+
## Benefits of tracking experiments
48+
49+
Whether you train models with jobs in Azure Machine Learning or interactively in notebooks, experiment tracking helps you:
50+
51+
- Organize all of your machine learning experiments in a single place. You can then search and filter experiments and drill down to see details about previous experiments.
52+
- Easily compare experiments, analyze results, and debug model training.
53+
- Reproduce or rerun experiments to validate results.
54+
- Improve collaboration, because you can see what other teammates are doing, share experiment results, and access experiment data programmatically.
55+
3256
## Tracking with MLflow
3357

58+
Azure Machine Learning workspaces are MLflow-compatible. This compatibility means you can use MLflow to track runs, metrics, parameters, and artifacts in workspaces without needing to change your training routines or inject any cloud-specific syntax. To learn how to use MLflow for tracking experiments and runs in Azure Machine Learning workspaces, see [Track experiments and models with MLflow](how-to-use-mlflow-cli-runs.md).
59+
3460
Azure Machine Learning uses MLflow tracking to log metrics and store artifacts for your experiments. When you're connected to Azure Machine Learning, all MLflow tracking materializes in the workspace you're working in.
3561

36-
To learn how to set up MLflow tracking for experiments and training routines, see [Log metrics, parameters, and files with MLflow](how-to-log-view-metrics.md). You can also [query and compare experiments and runs with MLflow](how-to-track-experiments-mlflow.md).
62+
To learn how to enable logging to monitor real-time run metrics with MLflow, see [Log metrics, parameters, and files with MLflow](how-to-log-view-metrics.md). You can also [query and compare experiments and runs with MLflow](how-to-track-experiments-mlflow.md).
3763

3864
MLflow in Azure Machine Learning provides a way to centralize tracking. You can connect MLflow to Azure Machine Learning workspaces even when you're working locally or in a different cloud. The Azure Machine Learning workspace provides a centralized, secure, and scalable location to store training metrics and models.
3965

0 commit comments

Comments
 (0)