search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.22k stars 21.38k forks source link

Audit trail section could use references #36279

Closed IvoMerchiers closed 5 years ago

IvoMerchiers commented 5 years ago

The section about 'Capture an end to end audit trail of the ML lifecycle' lacks some references. In particular the following list discusses three features/services without any links:

>- Azure ML Datasets help you track and version data. >- Azure ML Run History manages the code, data and compute used to train a model. >- The Azure ML Model Registry captures all of the metadata associated with your model (which experiment trained it, where it is being deployed, if its deployments are healthy).

A quick google also does not return useful results about what these concepts mean or where their documentation exists.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

RohitMungi-MSFT commented 5 years ago

@IvoMerchiers Thanks for the feedback. We are investigating into the issue and will update you shortly.

RohitMungi-MSFT commented 5 years ago

@jpe316 Could you please check if the requested content can be added to the documentation for reference?

j-martens commented 5 years ago

assign:blackmist

j-martens commented 5 years ago

@IvoMerchiers thank you for reporting this gap. We have added this request to the backlog to work on soon. If there is some info hidden somewhere else, I hope someone else on this thread will share a link or two.

Also note that: When you start a training run where the source directory is a local Git repository, information about the repository is stored in the run history. For example, the current commit ID for the repository is logged as part of the history. This works with runs submitted using an estimator, ML pipeline, or script run. It also works for runs submitted from the SDK or Machine Learning CLI.

j-martens commented 5 years ago

Thanks again. We will now proceed to close this thread. #please-close.