You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-monitor-model-performance.md
+18-9Lines changed: 18 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -819,7 +819,7 @@ You can also set up model monitoring for models deployed to Azure Machine Learni
819
819
* Register the production inference data as an Azure Machine Learning data asset, and ensure continuous updates of the data.
820
820
* Provide a custom data preprocessing component and register it as an Azure Machine Learning component.
821
821
822
-
You must provide a custom data preprocessing component if your data isn't collected with the [data collector](how-to-collect-production-data.md). Without this custom data preprocessing component, the Azure Machine Learning model monitoring system won't know how to process your data into tabular form with support for time windowing.
822
+
You must provide a custom data preprocessing component if your data isn't collected with the [data collector](how-to-collect-production-data.md). Without this custom data preprocessing component, the Azure Machine Learning model monitoring system can't process your data into tabular form with support for time windowing.
823
823
824
824
Your custom preprocessing component must have these input and output signatures:
825
825
@@ -832,21 +832,30 @@ Your custom preprocessing component must have these input and output signatures:
832
832
833
833
For an example of a custom data preprocessing component, see [custom_preprocessing in the azuremml-examples GitHub repo](https://github.com/Azure/azureml-examples/tree/main/cli/monitoring/components/custom_preprocessing).
834
834
835
+
For instructions for registering an Azure Machine Learning component, see [Register component in your workspace](how-to-create-component-pipelines-ui.md#register-component-in-your-workspace).
836
+
837
+
After you register your production data and preprocessing component, you can set up model monitoring.
838
+
835
839
# [Azure CLI](#tab/azure-cli)
836
840
837
-
Once you've satisfied the previous requirements, you can set up model monitoring with the following CLI command and YAML definition:
841
+
1. Create a monitoring definition YAML file that's similar to the following one. Before you use this definition, adjust the following values and any others you need to fit your environment:
838
842
839
-
```azurecli
840
-
az ml schedule create -f ./model-monitoring-with-collected-data.yaml
841
-
```
843
+
- For `endpoint_deployment_id`, use a value in the format `azureml:<endpoint-name>:<deployment-name>`.
844
+
- For `pre_processing_component`, use a value in the format `azureml:<component-name>:<component-version>`. Specify the exact version, such as `1.0.0`, not `1`.
845
+
- For each `path`, use a value in the format `azureml:<data-asset-name>:<version>`.
846
+
- For the `target_column` value, use the name of the output column that contains values that the model predicts, such as `DEFAULT_NEXT_MONTH`.
847
+
- For `emails`, list the email addresses that you want to use for notifications.
842
848
843
-
The following YAML contains the definition for modelmonitoringwith production inference data that you've collected.
0 commit comments