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.
Feel free to fork the repository or download the stable
release.
Insert your incident scenarios into the general_incidents.json
file inside the incidents/
folder. The file has the following format:
| 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. |
You could use general_incidents.jsonnet as an example in case you want to generate your incident scenarios using Jsonnet.
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.
Most importantly, have fun!
You can read a comprehensive example on how to conduct the exercise here.