← Latest papers
🤖 machine learning

When Drift Detectors cry Wolf: False Alarm Rates in continuous ML Monitoring

This paper empirically analyzes the false positive rates of five common drift detectors under continuous monitoring conditions, revealing that while PSI becomes reliable with larger batch sizes, other detectors exhibit persistent fluctuations, and applying statistical corrections like Bonferroni reduces false alarms at the cost of sensitivity, ultimately offering practical guidelines for balancing stability and sensitivity in production ML systems.

Original authors: Raj Shekhar Singh

Published 2026-07-21
📖 5 min read🧠 Deep dive

Original authors: Raj Shekhar Singh

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Background: When Computers Get Lost in Time

Imagine you hire a brilliant robot to sort apples from oranges. You train it in a quiet kitchen with perfect fruit, and it becomes a master. But then, you move that robot to a bustling, noisy supermarket where the apples are bruised, the oranges are smaller, and the lighting is different. Over time, the fruit changes shape, color, and texture. If the robot doesn't realize the world has shifted, it will keep sorting based on its old training, making mistakes until it fails completely. This is the world of Machine Learning Monitoring. In the real world, data isn't static; it drifts, like a river changing its course. To catch these changes, scientists use Drift Detectors, which are like security guards constantly comparing the new fruit arriving at the door against a photo of the "perfect" fruit from the past.

However, security guards can be jumpy. If a guard is too sensitive, they might scream "Intruder!" every time a leaf blows across the threshold. In the world of computers, this is called a False Alarm. If a system cries "wolf" too often, the human engineers who are supposed to fix the real problems get tired, annoyed, and eventually turn the alarms off. This is known as Alarm Fatigue. The big question isn't just "Can the computer spot a change?" but "Will it scream at us for nothing when we are watching it every single day?" This paper dives into that exact problem, asking how often these digital guards actually cry wolf when there is no wolf at all.

The Story: The Wolf-Crying Guards

The authors of this paper decided to put five popular "security guards" (drift detectors) through a grueling, month-long simulation to see how they behaved when left alone to watch a stream of data. They didn't just test them once; they simulated a 30-day continuous monitoring cycle, checking the data every day with different group sizes (batches) of information. They used a classic dataset about income and age, pretending that sometimes the data stayed the same (no drift) and sometimes it slowly changed (drift), just like real life.

The main finding is a bit of a shock to the industry: some of these guards are terrible at staying calm when the crowd is small.

The paper focuses on five specific detectors: PSI, KS, MMD, LSDD, and Adversarial Validation. Here is what they discovered about each one:

  • The Jumpy Guard (PSI): The Population Stability Index (PSI) turned out to be the most dramatic. When the group of data it was checking was small (fewer than 200 samples), it went crazy. In the simulation, if the batch size was between 50 and 100, this detector triggered an alarm almost every single day, even when the data hadn't changed at all. It was crying wolf constantly because it couldn't handle the "noise" of small numbers. However, the paper found a magic number: once the batch size grew past 200 samples, PSI suddenly calmed down and became very reliable. It's like a guard who panics if they only see three people, but becomes steady once they see a crowd of 200.

  • The Steady Guards (KS and LSDD): The Kolmogorov–Smirnov (KS) test and LSDD were much more chill. Even with small groups of data, they didn't scream as often as PSI. They offered a better balance, staying relatively quiet when things were normal but still loud enough to catch real changes. They are the "reliable default" choices for smaller datasets.

  • The Sleepy Guard (MMD): The Maximum Mean Discrepancy (MMD) was the opposite of the jumpy guard; it was almost too quiet. It rarely gave false alarms, which sounds great, but it also barely noticed the real changes the researchers tried to sneak in. It was so focused on not making mistakes that it missed the actual problems.

  • The Skeptical Guard (Adversarial Validation): This method, which uses a classifier to spot differences, was also very conservative. It only sounded the alarm when the changes were huge and obvious. It was great at avoiding false alarms, but it might miss subtle shifts that a human would notice.

The Trade-Off: Silence vs. Safety

The researchers also tested a rule called the Bonferroni correction. Think of this as making the security guard's rules much stricter. You tell the guard, "You can only scream if you are 99.9% sure." The paper found that this worked perfectly at stopping the false alarms—often bringing them down to near zero. But there was a catch: the guard also stopped noticing the real wolves. By making the system safer from false alarms, it became blind to real problems. This confirms a classic trade-off: you can have a system that is very stable (rarely cries wolf) or very sensitive (catches every change), but it is very hard to have both at the same time.

The Takeaway

The paper concludes that there is no "one-size-fits-all" security guard for machine learning. If you are monitoring a system with small batches of data (under 200 samples), you should avoid using PSI, or you will be stuck dealing with constant, annoying false alarms. Instead, you might want to use the KS test or accept that you need to wait for larger groups of data before trusting the alerts.

Ultimately, the authors show that in the real world of continuous monitoring, the way you configure these detectors matters more than we thought. If you don't tune them right, you risk either ignoring real problems because the alarms are too loud, or missing subtle dangers because the system is too quiet. The key is knowing your data's size and choosing the right guard for the job, rather than just hoping the alarm system works itself.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →