Chaos Toolkit is a project whose mission is to provide a free, open and community-driven toolkit and API to all the various forms of chaos engineering tools that the community needs.
The Chaos Toolkit has two main purposes:
- To provide a full chaos engineering implementation that simplifies the adoption of chaos engineering by providing an easy starting point for applying the discipline.
- To define an open API with the community so that any chaos experiment can be executed consistently using integrations with the many commercial, private and open source chaos implementations that are emerging.
Firstly the Chaos Toolkit aims to make it simple and straightforward to run experiments against your live system to build confidence in its behavior and learn about potential weaknesses.
Following the principles of chaos engineering, the Chaos Toolkit aims to be the easiest way to apply these principles to your own complex, and even sometimes chaotic, systems.
Secondly the Chaos Toolkit defines an open API to Chaos Engineering through it's JSON-format experiment definition. The toolkit can be extended to integrate with any number of commercial, private and open source chaos implementations through probes (to measure steady-state before and after an experiment) and actions (to vary real-world events during an experiment).
Before installing the Chaos Toolkit it is recommended that you create a Python virtual environment for running your chaos experiments. Full instructions for installing chaostoolkit and its requirements are available in the installation documentation.
Once you have installed the Chaos Toolkit you can use it through its simple command line tool. The tool's main job is to run your experiment and then generate a report of the findings from the experiment to then share with your team for discussion.
Running an experiment is as simple as:
$ chaos run experiment.json
The Chaos Toolkit takes experiments defined in a JSON format description file, encoded in JSON, and runs its steps sequentially. A full description of this JSON experiment description file can be found in the [main project documentation][experiment-description].
[experiment-description]: Provide a full experiment JSON description
The Chaos Toolkit plays the experiment JSON description that you provide to it. Experiments are made up of probes (to measure steady-state before and after an experiment) and actions (to vary real-world events during an experiment). We are always looking for community contribution and ideas around what probes and actions you might need as you integrate chaos experiments through the Chaos Toolkit, into your own unique context and evironment.
If you have an idea for a new set of probes and actions that you'd like to share, please first consider raising a ticket or even joining our community slack to suggest your idea. (As a hint, always @russmiles in the community Slack when you post your idea to get Russ's, and the team's, attention immediately! We want to hear from you).
In terms of implementation, the Chaos Toolkit currently supports probes and actions implemented as Python functions, separate processes or even remote HTTP calls. As long as your extensions conform to the Chaos Toolkit API you can then specify your own unique extensions in your experiment JSON definitions.
The core implementation of the Chaos Toolkit API can be found in the chaostoolkit-lib project.
The following free and open source extensions are available for your probes and/or actions:
- chaostoolkit-kubernetes: Kubernetes activities
- chaostoolkit-gremlin: Gremlin, Inc activities
- chaostoolkit-prometheus: Prometheus probes
Chaos Toolkit's mission is to provide an open API to chaos engineering in all its forms. As dsuch we encourage and welcome to you is open join our open community Slack team to discuss and share your experiments and needs with the community.
If you'd prefer not to use Slack then we welcome the raising of GitHub issues on this repo for any questions, requests, or discussions around the Chaos Toolkit.
Finally you can always email [email protected] with any questions or requirements as well.