What statistical methods automate canary-baseline comparison and handle noise?

WHAT THIS TESTS: This question probes whether you can replace human judgment in canary analysis with statistically sound automation. Interviewers want to see that you understand comparing two noisy production populations, controlling false positives when many metrics are evaluated, and isolating real regressions from transient infrastructure blips.

A GOOD ANSWER COVERS: First, choose the right statistical test. Because production latency and error rates are rarely normal, prefer non-parametric tests like the Mann-Whitney U test to compare the canary and baseline distributions without assuming Gaussian shape. If you use a t-test, cite Welch's version to handle unequal variance. Second, aggregate across metrics. A single failing metric should not necessarily kill a deployment, so adopt a scoring model like Kayenta's where each metric contributes to an aggregate score based on effect size and confidence, and the canary passes only if the composite score exceeds a threshold. Third, handle noise and spikes. Apply smoothing techniques such as moving medians or exponential smoothing before testing, reject outliers via Median Absolute Deviation thresholds, and consider trimming extreme percentiles. Fourth, control the multiple comparison problem. When testing dozens of metrics, use Bonferroni or False Discovery Rate corrections so that random noise does not guarantee a false alarm. Fifth, baseline hygiene. Deploy fresh baseline instances with the same code as production to avoid startup effect bias, and ensure both canary and baseline run for the same duration.

COMMON WRONG ANSWERS: A naive approach compares simple arithmetic means over a short window and fails if the canary average exceeds a fixed percentage. This ignores distribution shape, sample size, and variance. Another red flag is relying solely on p-values without measuring effect size; with large traffic volumes, even trivial differences become statistically significant. Proposing to test one global metric instead of per-metric aggregation also signals shallow experience.

LIKELY FOLLOW-UPS: How do you choose the canary traffic percentage and duration to achieve statistical power? What do you do when metrics are highly correlated and a single root cause triggers many alerts? How would you handle canary analysis for stateful services or batch jobs where traffic routing is not uniform?

ONE CONCRETE EXAMPLE: Suppose you are evaluating a new search ranking model. You route 1 percent of traffic to the canary and create three fresh baseline instances. For each of 20 metrics, you collect one-minute buckets over 30 minutes. You smooth each bucket with a five-minute moving median, remove outliers beyond three MAD, then run Mann-Whitney U per metric. You require both a p-value below 0.01 after Bonferroni correction and a Cohen's d effect size above 0.2 to flag a metric. Each flagged metric subtracts from a composite score. If the final score stays above the passing threshold, Spinnaker promotes the deployment automatically.

Source: cloud.google.com