This middleware handler will generate a fixed or random delay in the request/response chain once it is enabled.
The following is the config file.
# Light Chaos Monkey Latency Assault Handler Configuration.
# Enable the handler if set to true so that it will be wired in the handler chain during the startup
# Bypass the current chaos monkey middleware handler so that attacks won't be triggered.
# How many requests are to be attacked. 1 each request, 5 each 5th request is attacked
# Dynamic Latency range start in milliseconds. When start and end are equal, then fixed latency.
# Dynamic latency range end in milliseconds
Depending on the configuration, a random latency will be injected during the normal request flow. If one request is picked to trigger the assault, a random or fixed delay will be added before returning the response to the client.
In the centralized log, you should find the following info level statement.
Chaos Monkey - I am sleeping for 1000 milliseconds!
The number of milliseconds is a variable in the statement.
In the metrics, you should see the response time for the endpoint has a spike periodically.
For each client request, a timeout should be configured, and it should retry another server instance in the cluster.
If the timeout is not reached, then it is business as usual.