After having your experiment fully designed you can simply use the Run-button to execute it. This action can be performed if all the following conditions are met:
  1. 1.
    No validation errors
  2. 2.
    Every attack resolves at that moment to at least one target.
  3. 3.
    You are member of the same team as the experiment
  4. 4.
    Emergency stop has not been triggered.
Otherwise, you'll get an error message and the experiment is not started.
As soon as the experiment starts, the platform automatically switches over to the run view. The first step of the platform is to establish the connection to the matching agents. In addition, the running experiment is indicated at the top right run icon.
Experiment Run View
The run view consists of the following elements.
  • Experiment Player: At the top you see the sequence defined previously in the design. While the experiment is running a special marker indicates the current point of time. Some attacks need a little bit of extra time before being started which is indicated by a light green colouring in the front. The extra time is added to the timing of the attack and is currently caused by technical reasons.
  • Run Log: The run log lists more details to the experiment attacks and actions. For instance, you can see which exact containers are affected by the attack or what is the exact reason for a failed experiment
  • Deployment Replica Count: When using an experiment in a Kubernetes context we will automatically monitor how many PODs are ready in your cluster and indicate whenever there is a discrepancy.
  • Kubernetes Event Log: When using an experiment in a Kubernetes context we provide you access to the Kubernetes Events so that you can identify what exactly happens in the Kubernetes cluster.
  • HTTP Call: If your experiment contains a HTTP Call-action you can see the response time as well as HTTP response status as a separate widget in the run window.
  • Monitoring Events: In case your admin has installed a monitoring extension to Steadybit (see monitoring extensions in Reliability Hub) you can see occuring events and alerts of your setup directly in the run view.
Every experiment run has a unique identifier (e.g. #33131), which you can use to identify older experiment runs (visible on the left side).
Eventually, every experiment run ends in one of the following states:
End state
Entire experiment (all attacks, actions and checks) were successfully executed - so no failure reported by any check.
The experiment was canceled by user interaction and all attacks were rolled back.
The run failed due to some failing checks, for example a HTTP Check not reaching the required success rate.
The run failed due to some technical reasons like Failed attack execution or Agent disconnected unexpectedly. This shouldn't happen frequently, in case it does, let us know. We are constantly improving the platform to reduce failure states.
In case an agent looses the connection to the platform during an experiment, it will immediately stop and rollback running attacks. There are some attacks ( like Stop Container) which can't be rolled back due to it's nature.
Last modified 1mo ago