Wheel of Misfortune is a game that aims to build confidence to oncall engineers via simulated outage scenarios. With the game, you practice problem debugging under stress, the understanding of the incident management protocol, and effective communication with other engineers of your team and organization. It is a great way to train new hires, interns, and seasoned engineers to become well-rounded oncall engineers.
- Scenario: A past or fictional incident case.
- Game Master: The host-coordinator of the session.
- Volunteer: The trainee oncall engineer.
|title||the title of the incident.|
|scenario||the description of the incident. It is useful to include URLs from monitoring systems, dashboards, time-series databases and playbooks.|
|ID||the unique ID of the outage (you can just auto-increment).|
|inkstory||the path to an Ink story file in JSON format.|
Wheel of Misfortune also supports the Ink scripting language for writing incident response narratives, for team and invdividual training. Ink is a scripting language for writing interactive narrative stories. It enables us to write interactive incident response narratives for team or individual trainings. You can use Inky to write an interactive narrative for an incident and then export the story as JSON. Then, you can store the story file inside the incidents/ folder and associate the Ink story file with an Incident scenario using the inkstory key. You can have a look at the incident narrative example.
- Choose a volunteer to be the primary oncall engineer in front of the group.
- Find a balance between volunteer's experience and incident's difficulty.
- Assist volunteer by answering questions that may arise in each theoretical action or dashboard observation.
- Engage with the rest of the team and ask for different ways to debug the problem following the volunteer's explanation.
- Team members may be made available over time for assistance in various topics.
- Spin the wheel and attempt to fix the theoretical outage scenario.
- Explain to the Game Master and the rest of the group what actions you would take (lookup queries, checks in dashboards, etc.) to find the root causes, and eventually solve the incident.
- Always keep an eye on the time, since it is simulated incident response scenario and not a routine troubleshooting process. During a real incident you might have an SLA or SLO breach and therefore you should take timing into account.
- Engage with the rest of the group. Keep them in the loop. Ask questions to different members depending on their expertise.
Most importantly, have fun!
You can read a comprehensive example on how to conduct the exercise here.