After a canary deployment, error budgets burn and logs/metrics implicate the new Lambda version. What observability-backed action should the team take?
Select an answer to reveal the explanation.
Short Explanation
When the canary burns the error budget and the graphs blame the new version, roll traffic back to the prior alias. Observability is there so you can reverse course with evidence, not vibes.
Full Explanation
When canary metrics and logs show elevated errors against an error budget, the evidence-based mitigation is to shift traffic back to the previous Lambda alias or version. Increasing canary weight, disabling monitoring, or deleting shared data stores worsens impact rather than containing the bad release.