Model Drift Detection

When ML models are deployed in production, sometimes even minor changes in a data distribution can adversely affect the performance of ML models. When the input data distribution shifts then prediction quality can drop. It is important to track this drift. This demo is based on the mixed-type tabular data drift detection method in the alibi detect project for tabular datasets.

Here we will :

  • Launch an income classifier model based on demographic features from a 1996 US census. The data instances contain a person’s characteristics like age, marital status or education while the label represents whether the person makes more or less than $50k per year.

  • Setup a mixed-type tabular data drift detector for this particular model.

  • Make a batch of predictions over time

  • Track the drift metrics in the Monitoring dashboard.

Register an income classifier model

Register a pre-trained income classifier SKLearn model with model artefacts stored publicly in this Google bucket: gs://seldon-models/scv2/samples/mlserver_1.4.0/income-sklearn/classifier/

  1. In the Model Catalog page, click the Register New Model button:

    Expand to see the 'Register New Model' button

    register new model button

  2. In the Register New Model wizard, enter the following information, then click REGISTER MODEL:

    • Model Name: income-classifier

    • URI: gs://seldon-models/scv2/samples/mlserver_1.4.0/income-sklearn/classifier/

    • Artifact Type: SciKit Learn

    • Version: v1

    Expand to see model configuration../../../../_images/configure-model1.png

Configure predictions schema for classifier

Edit the model metadata to update the prediction schema for the model. The prediction schema is a generic schema structure for machine learning model predictions. It is a definition of feature inputs and output targets from the model prediction. Use the income classifier model predictions schema to edit and save the model level metadata. Learn more about the predictions schema at the ML Predictions Schema open source repository.

  1. Click on the model income-classifier model that you have just registered.

    Expand to see select model

    select model

  2. Click the Edit Metadata button to update the prediction schema associated with the model

  3. Paste the prediction schema and click Save Metadata.

    Expand to see configure prediction schema../../../../_images/configure-prediction-schema-v2.png

Launch a Seldon ML Pipeline

Deploy the income classifier model from the catalog into an appropriate namespace

  1. From the model catalog, under the Action dropdown list, select Deploy.

    Expand to see deploy model

    deploy model

  2. Enter the deployment details in the deployment creation wizard and click Next:

    • Name: income-drift-demo

    • Type: Seldon ML Pipeline

    Expand to see deploy model

    In the deployment creation wizard, enter a name for your new deployment (e.g. income-drift-demo). Select the namespace you would like the deployment to reside in (e.g. seldon) and click Next. income drift demo wizard

  3. The predictor details should already be filled in from the model catalog. Click Next:

    Expand to see default predictor details

    income drift demo predictor details

  4. Click Next for the remaining steps, then click Launch.

Add A Drift Detector

From the deployment overview page, select your deployment to enter the deployment dashboard. Inside the deployment dashboard, add a drift detector with by clicking the Create button within the DRIFT DETECTION widget.

Expand to see drift detector creation

configure drift detector

create drift detector

Enter the following parameters in the modal popup which appears, to configure the detector:

  • Detector Name: income-drift.

  • Model URI: (For public google buckets, secret field is optional)

  • Reply URL: (By default, the Reply URL is set as seldon-request-logger in the logger’s default namespace. If you are using a custom installation, please change this parameter according to your installation.)

  • Minimum Batch Size: 200

  • Drift Type: Feature

Then, click CREATE DETECTOR to complete the setup.

Configure predictions schema for detector

As per the income classifier model, use the same model predictions schema to edit and save the model level metadata for drift detector.

  1. Click on the vertical ellipses “⋮” icon for the drift detector you have just registered.

    Expand to see the dropdown for the Detector

    select detector

  2. Click the Configure Metadata option to update the prediction schema associated with the model

  3. Paste the prediction schema, name the model income-drift and click Save Metadata.

    Expand to see configure prediction schema../../../../_images/configure-prediction-schema-drift-v2.png

Run Batch Predictions

  1. From the deployment dashboard, click on Batch Jobs. Run a batch prediction job using the V2 payload format text predictions data file. This file has 4000 individual data points and based on our drift detector configuration, drift will be detected for a batch every 200 points. The distribution of the data in the first half section is the same as the distribution of the reference data the drift detector was configured with and the second half section of the data should be different to observe drift.

  2. Upload the data to a bucket store of your choice. This demo will use MinIO and store the data at bucket path minio://income-batch-data/data.txt . Do not forget to configure your storage access credentials secret - we have it as minio-bucket-envvars here. Refer to the batch request demo for an example of how this can be done via the minio browser.

  3. Running a batch job with the configuration below. This runs an offline job that makes a prediction request for a batch of 200 rows in the file at minio://income-batch-data/data.txt every 5 seconds:

    Input Data Location: minio://income-batch-data/data.txt
    Output Data Location: minio://income-batch-data/output-{{}}.txt
    Number of Workers: 1
    Number of Retries: 3
    Batch Size: 200
    Minimum Batch Wait Interval (sec): 5
    Method: Predict
    Transport Protocol: REST
    Input Data Type: V2 Raw
    Storage Secret Name: minio-bucket-envvars

Monitor Drift Detection Metrics

Under the Monitor section of your deployment navigation, on the Drift Detection Tab, you can see a timeline of drift detection metrics.

The drift dashboard showcases 2 types of metrics graphs:

  1. P-value score over time

    1. Zoomed in view, focusing on features that have drifted, i.e. features that have a p-value score of less than the threshold. p-values drift metrics zoomed in

    2. Zoomed out view, showing all features p-values drift metrics zoomed out

  2. Distance score over time. distance score metrics

Monitor Drift Detection Alerts

If you have alerting configured you should see a notification about the drift

alert notification

with further details present on the alerting log

alert notification

Data drift and reference distributions comparison

To further analyse prediction data drift, you can also switch to the feature distribution tab to compare predictions to reference data distribution. See feature distribution monitoring demo for setup details.

Upload the income classifier reference dataset as the reference data to monitor data drift in terms of feature distributions. Once reference data is available, you can compare the distributions of the prediction data to the reference data.

Expand to see reference data available

You can see when reference data is available by checking the button on the top left of the DISTRIBUTIONS dashboard. If it is not clickable and displays REFERENCE DATA AVAILABLE, then reference data is available.

Reference data available button

For each feature, you can click on Toggle reference data to view reference data side by side.

monitor distributions

We will see that the drifted data has lower education individuals that were not in the reference data.


If you experience issues with this demo, see the troubleshooting docs or Elasticsearch sections.