Comment on page
Evidently and MLflow
Log Evidently metrics in the MLflow UI.
TL;DR: You can use Evidently to calculate metrics, and MLflow Tracking to log and view the results.
Jupyter notebook with en example:
Many machine learning teams use MLflow for experiment management, deployment, and as a model registry. If you are already familiar with MLflow, you can integrate it with Evidently to track the performance of your models.
In this case, you use Evidently to calculate the metrics and MLflow to log the results. You can then access the metrics in the MLflow interface.
Evidently calculates a rich set of metrics and statistical tests. You can choose any of the pre-built reports or combine individual metrics to define what you want to measure. For example, you can evaluate prediction drift and feature drift together.
You can then generate the calculation output in a Python dictionary format. You should explicitly define which parts of the output to send to MLflow Tracking.
In this tutorial, you will use Evidently to check input features for Data Drift and log and visualize the results with MLflow.
Here is a Jupyter notebook with the example:
In case of any discrepancies refer to the example notebook as a source of truth.
Evidently is available as a PyPI package:
$ pip install evidently
To install MLflow, run:
$ pip install mlflow
Or install MLflow with scikit-learn via
$pip install mlflow[extras]
For demonstration purposes, we treat this data as the input data for a live model. To use with production models, you should make your prediction logs available.
This is how it looks:
You should specify the categorical and numerical features so that Evidently performs the correct statistical test for each of them. While Evidently can parse the data structure automatically, manually specifying the column type can minimize errors.
data_columns = ColumnMapping()
data_columns.numerical_features = ['weathersit', 'temp', 'atemp', 'hum', 'windspeed']
data_columns.categorical_features = ['holiday', 'workingday']
Specify which metrics you want to calculate. In this case, you can generate the Data Drift report and log the drift score for each feature.
def eval_drift(reference, production, column_mapping):
data_drift_report = Report(metrics=[DataDriftPreset()])
data_drift_report.run(reference_data=reference, current_data=production, column_mapping=column_mapping)
report = data_drift_report.as_dict()
drifts = []
for feature in column_mapping.numerical_features + column_mapping.categorical_features:
drifts.append((feature, report["metrics"][1]["result"]["drift_by_columns"][feature]["drift_score"]))
return drifts
You can adapt what you want to calculate by selecting a different Preset or Metric from those available in Evidently.
Specify the period that is considered reference: Evidently will use it as the base for the comparison. Then, you should choose the periods to treat as experiments. This emulates the production model runs.
#set reference dates
reference_dates = ('2011-01-01 00:00:00','2011-01-28 23:00:00')
#set experiment batches dates
experiment_batches = [
('2011-01-01 00:00:00','2011-01-29 23:00:00'),
('2011-01-29 00:00:00','2011-02-07 23:00:00'),
('2011-02-07 00:00:00','2011-02-14 23:00:00'),
('2011-02-15 00:00:00','2011-02-21 23:00:00'),
]
Initiate the experiments and log the metrics calculated with Evidently on each run.
#log into MLflow
client = MlflowClient()
#set experiment
mlflow.set_experiment('Data Drift Evaluation with Evidently')
#start new run
for date in experiment_batches:
with mlflow.start_run() as run: #inside brackets run_name='test'
# Log parameters
mlflow.log_param("begin", date[0])
mlflow.log_param("end", date[1])
# Log metrics
metrics = eval_drift(raw_data.loc[reference_dates[0]:reference_dates[1]],
raw_data.loc[date[0]:date[1]],
column_mapping=data_columns)
for feature in metrics:
mlflow.log_metric(feature[0], round(feature[1], 3))
print(run.info)
You can then use the MLflow UI to see the results of the runs. You can use the menu to select which metrics calculated by Evidently you'd want to see. In this example, you can choose drift for which features to display:
This is an additional tutorial that demonstrates how you can evaluate historical drift in your data. It also shows how to log experiments with MLflow in a similar fashion. In this example, instead of logging drift scores for individual features, it logs the "Dataset drift" metric:
Last modified 11mo ago