What signals indicate a canary rollout should pause or rollback?

What signals indicate a canary rollout should pause or rollback?

• A. Error rate increases, latency spikes, or user impact worsens.
• B. All metrics improve immediately.
• C. No changes at all.
• D. Rollout speed increases.

Answer: (A)

During a canary rollout, you monitor reliability and performance on a small user segment. If the new version causes more errors, latency spikes, or user experience worsens, those signals show the change is harming customers, so you should pause or roll back. These metrics directly reflect whether the service still meets its performance and reliability targets, making them the clearest indicators that something isn’t right and a reversal is warranted. If all metrics improve immediately, there’s no issue to stop for, and if there are no changes at all, there’s nothing to react to yet. Increasing rollout speed isn’t a reliability signal and could mask problems, so it doesn’t prompt a pause. Having automated thresholds, alerting, and a rollback plan helps you act quickly when negative signals appear.

During a canary rollout, you monitor reliability and performance on a small user segment. If the new version causes more errors, latency spikes, or user experience worsens, those signals show the change is harming customers, so you should pause or roll back. These metrics directly reflect whether the service still meets its performance and reliability targets, making them the clearest indicators that something isn’t right and a reversal is warranted. If all metrics improve immediately, there’s no issue to stop for, and if there are no changes at all, there’s nothing to react to yet. Increasing rollout speed isn’t a reliability signal and could mask problems, so it doesn’t prompt a pause. Having automated thresholds, alerting, and a rollback plan helps you act quickly when negative signals appear.