← All drillsBuild a Model Monitor
What you'll be able to do- ✓Build a run log that lets you replay a training run and get the same metrics, and show what it fails to protect
- ✓Detect a shifted input with PSI and a KS test, and measure how late each detector notices
- ✓Monitor a model without labels using input, missing-value and score distributions
- ✓Tell an upstream data bug from a real change in the applicant population
- ✓Set alert thresholds that survive checking twenty features a week
- ✓Write the response runbook as code and run it against forty simulated weeks
Run the monitoring a deployed model needs — log every run so it can be replayed, watch the inputs and scores for drift without labels, and turn each alert into the right action instead of a reflex retrain.
⌁ The ML observability and tracking behind production models — Arize, Evidently, Fiddler and Databricks (MLflow) — wherever a model must be reproducible and its live inputs watched.
Start this internshipCreate an account to unlock the 4 sections, the workbench, and askThili.
BeginSections
1. Build a Model Monitor
🔒 locked2. Lesson 1 - A run you can replay
🔒 locked3. Lesson 2 - Does today look like training?
🔒 locked4. Lesson 3 - An alert that people keep reading
🔒 lockedDig deeper
📄Hidden Technical Debt in Machine Learning Systems (Sculley et al., 2015, NeurIPS)
paper📄A Survey on Concept Drift Adaptation (Gama et al., 2014, ACM Computing Surveys 46(4))
paper📄Failing Loudly: An Empirical Study of Methods for Detecting Dataset Shift (Rabanser, Günnemann & Lipton, arXiv:1810.11953)
paper