ALFI is currently in an open beta.
To use ALFI, you must first integrate the Gremlin libraries into your application and redeploy. Please see the JVM Installation Guide for more details. Once you have successfully integrated the library, you should see logging like this:
1INFO com.gremlin.GremlinServiceFactory - Gremlin enabled for Team abcdefgh-1234-9876-3333-nopqrstuvwxy
Now you can start creating attacks from the Web UI. Here you will see a history of ALFI attacks run by your team.
Once you click
New ALFI Attack, you will receive a form with
Traffic Type, and
This section provides a way to determine which applications are eligible for the ALFI attack.
Upon application startup, the ALFI code running in each application creates an instance of
ApplicationCoordinates and passes that to the Gremlin API. Each
ApplicationCoordinates instance is eligible to pick up an ALFI attack. Please see Application Coordinates Setup for details on how to populate
The ALFI library comes with two Application Types out of the box: AWS Lambda and AWS EC2. Custom Application Types can also be created from your application, which can then be used in the Web UI with the
Add Custom Field button. Keep in mind that the most effective chaos experiments start small, so keep your custom Application Types as specific as possible.
This section provides a way to select individual requests within your application and only impact that set.
Any attribute which you have supplied in a
TrafficCoordinates is eligible to use in constructing the attack. Please see Traffic Coordinates Setup and Attaching Request Context data to all TrafficCoordinates for details on how to control the data being placed into a
The ALFI library includes integrations for the Apache HTTP client and Dynamo DB client (with more to come!), however you are free to create any sort of Traffic Type you would like and use those custom fields as attributes of the attack.
For Traffic Type, you may also supply a
Percentage of Traffic value. As probability is used to target this percentage, the actual impact may not exactly reflect the value specified.
This section provides a way to declare what impact you would like to inject.
You may choose an amount of latency to inject as well as a yes/no switch on whether you want this call to fail. These can also be combined to simulate a slow call which eventually fails. This impact gets applied to all traffic which matches the Traffic Type you've described above on the Application Type you've described above.
In this section, you also are required to declare the duration of the attack. For this duration, the attack is active and ALFI-enabled applications are impacted. As soon as the duration elapses, the applications no longer know about the attack and are no longer impacted.
Once you press the
Unleash Gremlin button, the attack becomes active and applications will start picking it up. Here you can see all of the attributes used in scoping the attack, as well as what the impact is and the duration of the attack. The attack then starts progressing through different phases of its lifecycle, as described here:
|Pending||Created but no applications have picked up the attack|
|Distributed||At least one application has picked up the attack, but none have been impacted|
|Impacted||At least one application has picked up the attack and been impacted|
|Successful||Impact was applied and duration elapsed|
|ApplicationNotFound||No application ever picked up the attack and duration elapsed|
|TrafficNotFound||No application ever applied impact and duration elapsed|
|Halted||Attack was halted (by UI or API) prior to the duration elapsing|