You are running an experiment to see whether your users like a new feature of a web application. Shortly after deploying the feature as a canary release, you receive a spike in the number of 500 errors sent to users, and your monitoring reports show increased latency. You want to quickly minimize the negative impact on users. What should you do first?

Question

Accepted Answer

A. Roll back the experimental canary release. A canary release is designed to test new features with a small subset of users and provides a quick rollback mechanism if issues arise. Rolling back the experimental canary release immediately removes the faulty code from production, stopping the negative impact (500 errors, increased latency) on users and preventing further degradation of service.

Answer

B. Start monitoring latency, traffic, errors, and saturation. Monitoring these metrics should already be in place as part of standard operations and certainly before/during a canary release; starting to monitor them now is too late to mitigate an active incident.

Answer

C. Record data for the postmortem document of the incident. Recording data for a postmortem is an important step *after* the incident is stabilized or resolved, not the first action to take when actively minimizing user impact.

Answer

D. Trace the origin of 500 errors and the root cause of increased latency. Tracing the root cause is crucial for a permanent fix and preventing recurrence, but it's a diagnostic step that comes after immediate mitigation to restore service.

You are running an experiment to see whether your users like a new feature of a web application. Shortly after deploying the feature as a canary release, you receive a spike in the number of 500 error

Question

Options

How the community answered

Why each option

Topics

Community Discussion