Mitigate first
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
restore service before finding the root cause.
Planned topics
- Mitigation options in order of speed and safety: rollback, disable a feature flag, scale or restart, fail over, shed load.
- Root cause analysis waits until users are no longer hurt.
- Keep evidence (logs, dashboards, heap dumps) before restarting if it is cheap to do so.
- Verify the mitigation worked using the SLI, not a feeling.
Draft outline details
Demonstration
decision list: "recent deploy? roll back. New feature? flag off. Load spike? scale or limit."
Check your understanding
Why not debug root cause first?
Show answer
Users stay harmed while you investigate.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.