AI 모델 모니터링

It can track data quality, distribution changes, prediction patterns, and measured outcomes. A change in input distribution is a reason to investigate, not automatic proof that accuracy has deteriorated.

주요 시사점

• Monitor input contracts and outcomes.
• Keep label delays and sample limits visible.
• Choose recovery based on the cause.

Establish a baseline from a documented period and model version. Track missing fields, invalid ranges, new categories, latency, and output distributions. These signals can detect pipeline failures before enough outcome labels are available to assess predictive quality. When reliable outcomes arrive, compare performance with the original evaluation and with relevant recent periods. Report subgroup results and sample sizes. Delayed or selectively collected labels can make a dashboard look more complete than its evidence supports. Distinguish data drift from changes in the relationship between inputs and outcomes. A seasonal shift may be expected, while a changed feature definition may indicate a software defect. Investigate the cause before choosing retraining as the response. Define alert thresholds, review responsibility, and a recovery decision. Responses can include correcting data, rolling back a release, changing a threshold, or retraining. Verify the intervention on appropriate evaluation material and continue measuring afterward. Monitoring should lead to informed action rather than automatic model churn.

1. Imagine the mean value of a temperature feature increasing sharply overnight.
2. Check whether the sensor changed from Celsius to Fahrenheit before concluding that the environment changed.
3. If the unit conversion is the cause, repair the pipeline and replay affected inputs; retraining on the mistaken values would address the wrong problem.

The constructed scenario connects monitoring to diagnosis and a proportionate fix.