Skip to main content
In this section, we provide guides and references to use the MLflow connector. Configure and schedule MLflow metadata and profiler workflows from the OpenMetadata UI:

​
Requirements

To extract metadata, OpenMetadata needs two elements:
  • Tracking URI: Address of local or remote tracking server. More information on the MLflow documentation here
  • Registry URI: Address of local or remote model registry server.

​
Metadata Ingestion

​
Connection Details

1

Connection Details

When using a Hybrid Ingestion Runner, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format:
This applies only to fields marked as secrets in the connection form (these typically mask input and show a visibility toggle icon). For a complete guide on managing secrets in hybrid setups, see the Hybrid Ingestion Runner Secret Management Guide.
  • trackingUri: Mlflow Experiment tracking URI. E.g., http://localhost:5000
  • registryUri: Mlflow Model registry backend. E.g., mysql+pymysql://mlflow:password@localhost:3307/experiments
2

Test the Connection

Once the credentials have been added, click on Test Connection and Save the changes.Test Connection
3

7. Configure Metadata Ingestion

In this step we will configure the metadata ingestion pipeline, Please follow the instructions belowConfigure Metadata Ingestion
4

Schedule the Ingestion and Deploy

Scheduling can be set up at an hourly, daily, weekly, or manual cadence. The timezone is in UTC. Select a Start Date to schedule for ingestion. It is optional to add an End Date.Review your configuration settings. If they match what you intended, click Deploy to create the service and schedule metadata ingestion.If something doesn’t look right, click the Back button to return to the appropriate step and change the settings as needed.After configuring the workflow, you can click on Deploy to create the pipeline.Schedule the Workflow
5

View the Ingestion Pipeline

Once the workflow has been successfully deployed, you can view the Ingestion Pipeline running from the Service Page.View Ingestion Pipeline
If AutoPilot is enabled, workflows like usage tracking, data lineage, and similar tasks will be handled automatically. Users don’t need to set up or manage them - AutoPilot takes care of everything in the system.