Understanding Scenarios

A Scenario is a set of Status Checks and Gremlin attacks that you define with a name, description, hypothesis, and detailed results. Once created and configured, a Scenario is run through a sequence of attacks with an expanding blast radius (number of hosts included in the attack) and magnitude (intensity of the attack). After each run of a Scenario, you can easily record your observations as well as edit the Scenario to expand the blast radius and magnitude to iterate on the experiment.

Scenarios can be used to recreate a past outage that impacted your system, or it can be used to automate a sequence of attacks to iteratively grow the blast radius of a Chaos Engineering experiment.

Scenarios allow you to link attacks together, growing both the blast radius and magnitude over time. Once created, these Scenarios become a shareable resource for your team, complete with a name, description, hypothesis, and a place to record your notes and observations.

With Scenarios, users can create a sequence of attacks and increase the blast radius and magnitude.

Inside Gremlin you will also find Recommended Scenarios, these are based on real-world outages, which allow for validation of a systems' ability to withstand each of the scenarios and avoid costly downtime.

Recommended Scenarios guide you through Chaos Engineering experiments to be sure that your application is reliable despite resource constraints, unreliable networks, unavailable dependencies, and more, preventing these types of outages from affecting your business and your customers.

After creating, running, and adding results to a Scenario you can, schedule it to run on an on-going basis to verify the results of your Scenario and prevent drifting into failure. Select the days of the week you would like it to run, the maximum number of times it can run, and the time window in which it can run.