> For the complete documentation index, see [llms.txt](https://docs.vectice.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectice.com/25.2/log-and-manage-assets-with-vectice-api/log-assets-to-vectice/log-mlflow-runs.md). # Log MLFLow runs Vectice provides an easy way to retrieve already saved information from your MLflow runs and document them into Vectice. To log model information from `MLFlow` use the following lines of code: ```python # Use the following model wrapper to retrieve your MLFlow run artifacts model = Model.mlflow(run_id='your_run_id', client=mlflow, url='https://your_url.com') # Log MLFlow artifacts in Vectice iteration.log(model) ```

Parameter	Description	Default
`run_id`	A unique identifier for the MLflow experiment run.	required
`client`	The MLflow client object used for interacting with MLflow. This parameter is mandatory to ensure compatibility and avoid issues with specific configurations.	required
`url`	The URL to the`MLFlow` UI to access the run information.	optional
`derived_from`	List of datasets (or version ids) to link as lineage.	optional

You can access your MLFlow run artifacts in Vectice where you will see the model version metrics, properties, and a link to the MLFlow UI of your run. Find this information by navigating to **Models** **>** **Select model name > Select version**.

MLFlow Model Version Metrics and Properties in the Vectice App

MLFlow UI URL Accessible in the Vectice App

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.vectice.com/25.2/log-and-manage-assets-with-vectice-api/log-assets-to-vectice/log-mlflow-runs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.