Neptune + MLflow integration
Neptune is a lightweight experiment tracker that offers a single place to track, compare, store, and collaborate on experiments and models.
This integration lets you enjoy tracking and reproducibility of MLflow with the organization and collaboration of Neptune. You can have your MLflow experiment runs hosted in a knowledge repo where you can invite and manage project contributors, while not having to change your MLflow logging code.
Should you wish to switch to Neptune, you can migrate your MLflow data to Neptune with the exporter tool.
What will you get with this integration?
- A plugin which you can use to send your MLflow-logged metadata to Neptune with the help of a tracking URI.
- An exporter for migrating existing MLflow experiments to your Neptune project.
Resources
Example
On the command line:
pip install neptune-mlflow
Send your MLflow-logged metadata to Neptune (in Python):
import mlflow
from neptune_mlflow_plugin import create_neptune_tracking_uri
# Create a Neptune tracking URI
neptune_uri = create_neptune_tracking_uri(
api_token=ANONYMOUS_API_TOKEN, # Set as environment variable or replace with your own token
project="common/mlflow-integration", # Set as environment variable or replace with your own project
tags=["mlflow", "plugin"], # (optional) use your own
)
mlflow.set_tracking_uri(neptune_uri)
with mlflow.start_run():
...
Export existing MLflow runs to Neptune:
neptune mlflow --project your-neptune-workspace/your-neptune-project
Support
If you got stuck or simply want to talk to us, here are your options:
- Check our FAQ page
- You can submit bug reports, feature requests, or contributions directly to the repository
- Chat! When in the Neptune application click on the blue message icon in the bottom-right corner and send a message. A real person will talk to you ASAP (typically very ASAP)
- You can just shoot us an email at support@neptune.ai
Metadata
Release files for neptune-mlflow 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| neptune_mlflow-1.1.1.tar.gz | 16.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neptune_mlflow-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.1 kB
Release files / neptune_mlflow-1.1.1.tar.gz
| Download URL | neptune_mlflow-1.1.1.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab470a016a767ea861aea4b67f408e9f7ab61023755df18bbbaa89642f9957de
|
|
BLAKE2b-256 checksum How to use checksums |
0c4e7d9d67769c72876092bf5fb6bf9a6c422fba04cf2dfdb99b4bcdd5e3d4a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / neptune_mlflow-1.1.1-py3-none-any.whl
| Download URL | neptune_mlflow-1.1.1-py3-none-any.whl |
|---|---|
| Size | 25.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db653ceecbb007cd120333e41c8b26d53a21ab9762e9c215005f1b293dfce301
|
|
BLAKE2b-256 checksum How to use checksums |
a4a0c79a0ecb8bf049988090b9214b486c092934193aca0e65c6cf1dbde0cc64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for neptune-mlflow 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.