## What is Monitoring and Managing Drift all about?
1. _MonitoringDrift_: You want to know that there might be a problem with the quality of your model _before_
1. your (internal or external) partners notice
1. your users notice
1. you lose trust
1. your business is impacted
1. you are in the news
2. _Managing Drift_: Once noticed, you want to be able to react quickly and effectively
1. analyze if there is a problem in the first place
1. if so, what to do about it
## How to prepare
* install the project as described in the readme:
https://github.com/DJCordhose/mlops-drift/blob/main/README.md#installation
* do not stress yourself, if you can not get this up and running
* there will be time for this in the workshop (even though not a lot)
* you can also just watch and learn, you will get a lot of benefit even without running the code
* the second part should work entirely without a local installation
* when forming teams, it is sufficient to have one person with a working installation
## What else can be monitored?
* Quality of the data
* how do missing or wrong fields change
* plausibility
* When you have Ground Truth
* Metric for the quality of the prediction as used in training
* Different typical quality metrics
* Caution: no matter how good the metric, it is again only a surrogate for the quality of the prediction
* Which model/fallback was used
* Requests per minute/hour/day
* Latency
* Error Rate
* User Feedback
* Lastly, there is the business or product KPI:
https://www.evidentlyai.com/blog/ml-monitoring-metrics#4-business-metrics-and-kpi
### What else / more material