The Gremlin Client is what interacts with your stack to inject failure. Once the client is installed within your infrastructure and authenticated with the Gremlin Control Plane, attacks can be thoughtfully planned, configured, and executed from the UI, API, or CLI.

An architectural diagram showing multiple clouds and vendors and how Gremlin operates with them


All Gremlin clients authenticated to the Gremlin Control Plane appear on the Clients view in the UI. You can only run attacks on clients that are active.

The other possible states are unhealthy and idle. An unhealthy client may not have been installed or configured correctly. A client enters an idle state once there is no activity for at least 5 minutes. You cannot run or schedule attacks on idle clients. If a client is idle for at 24 hours it will be removed from the Clients view. However, if a client communicates again with Gremlin while in the idle window, the client is reactivated.

Deactivating a Client

A client can be manually deactivated at any time. Simply find the client in question in the client list and click on the Deactivate button. To place the client back into a active state, click on the Activate button.