A monitor crosses its threshold. What should happen?
Why C is the answer
An alert or a retraining trigger
A monitor is only useful if crossing its threshold starts something, such as an alert or a retraining run.
In detail
- A monitor should cause an action: an alert or a retraining trigger.
- Tune thresholds, so alerts stay meaningful.
Use case
An illustrative scenario, not a real incident.
A drift monitor crosses its threshold. An alert reaches the team, and a retraining pipeline starts.
See it in different ways
flowchart LR A["Train"] --> B["Track with MLflow"] B --> C["Register a version"] C --> D["Deploy"] D --> E["Monitor"] E -->|"Threshold exceeded"| A
stateDiagram-v2 [*] --> Trained Trained --> Registered: version and lineage Registered --> Deployed Deployed --> Monitored Monitored --> Retrained: drift alert Retrained --> Registered Deployed --> Archived: replaced
flowchart LR S0["Metric crosses threshold"] --> S1["Alert"] --> S2["Retraining pipeline"] --> S3["Evaluation"]
Key point: A monitor should trigger an action.
Why the other options are wrong
- A. Nothing, until the next annual review of the model
- Waiting a year ignores the warning.
- B. A manual check of each prediction by the team
- Checking each prediction by hand does not scale.
- D. Automatic deletion of the production model
- Deleting the model causes an outage.