Level 4 · Monitoring, Drift & Operating ML at Scale¶
Level 4 is about the question a working deployment pipeline doesn't answer on its own: is the model still actually good, right now, with today's real data — not the data it was trained on? This level builds real drift detection, real monitoring that doesn't require waiting for ground-truth labels, and a real, deliberate decision process for when to retrain.
What was run, and what wasn't
This level computes real statistical drift measures against real, deliberately-shifted data, and builds real monitoring and alerting logic around a real served model. A full, large-scale production monitoring platform was not run as part of this course; the real statistical and architectural mechanisms underneath one are built and verified directly instead.
Prerequisites: Levels 1–3.
Modules¶
- Why Monitoring a Model Differs From a Service: a real case where a model can be "up" and fully healthy by every infrastructure metric while being badly wrong.
- Data Drift: When the Input Distribution Changes: real, measured drift in real input data, detected statistically.
- Concept Drift: When the Relationship Itself Changes: a real case where the inputs look the same but what they predict has genuinely changed.
- Model Performance Monitoring Without Ground Truth: real proxy signals used to catch real degradation before true labels ever arrive.
- Alerting on Model Degradation: a real alert that fires against a real, injected model degradation.
- Retraining Triggers: When and How to Retrain: a real, principled decision process, not a fixed retraining schedule.
- Model Governance & Auditability: a real, complete audit trail for one real model's entire lifecycle.
- Cost & Latency Tradeoffs in Model Serving: a real, measured tradeoff between model size, latency, and serving cost.
- Common MLOps Anti-Patterns: real, measured costs of getting this wrong, tallied from across the whole course.
- Capstone: A Complete MLOps Loop for a Real Model: tracking, registry, pipeline, and monitoring, for one real model, end to end.
After Level 4¶
You've tracked a real model, registered and served it, automated its deployment, and built real monitoring to catch it degrading — the same loop a real production ML team runs continuously, just at a scale you can finish on a laptop.