Skip to main content

Chaos engineering toolkit

Project description

# Chaos Toolkit - An Open API for Chaos Engineering

[![Build Status](https://travis-ci.org/chaostoolkit/chaostoolkit.svg?branch=master)](https://travis-ci.org/chaostoolkit/chaostoolkit) [![Docker Pulls](https://img.shields.io/docker/pulls/chaostoolkit/chaostoolkit.svg)](https://hub.docker.com/r/chaostoolkit/chaostoolkit/) [![Python versions](https://img.shields.io/pypi/pyversions/chaostoolkit.svg)](https://www.python.org/) [![Requirements Status](https://requires.io/github/chaostoolkit/chaostoolkit/requirements.svg?branch=master)](https://requires.io/github/chaostoolkit/chaostoolkit/requirements/?branch=master) [![Has wheel](https://img.shields.io/pypi/wheel/chaostoolkit.svg)](http://pythonwheels.com/)

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.

## Why the Chaos Toolkit?

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.

![Chaos Toolkit](https://chaostoolkit.org/static/chaos-toolkit-schema.fbdfc57a.svg)

### Simplifying Adoption of Chaos Engineering

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][principles], the Chaos Toolkit aims to be the easiest way to apply these principles to your own complex, and even sometimes chaotic, systems.

[principles]: http://principlesofchaos.org/

### An Open API to Chaos Engineering

Secondly the Chaos Toolkit defines an [Open API][api] to Chaos Engineering through it’s JSON/YAML-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).

[api]: http://chaostoolkit.org/reference/api/experiment/

## Install or Upgrade

Generally speaking, you can install it as follows:

` $ pip install -U chaostoolkit `

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][install].

[install]: http://chaostoolkit.org/reference/usage/install/

## Getting Started

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][json] description file, encoded in JSON (YAML is also supported), and runs its steps sequentially. A full specifiction of this experiment description file can be found in the [main project documentation][api].

[json]: https://www.json.org/

![Chaos Toolkit Run Sample](https://github.com/chaosiq/demos/raw/master/openfaas/experiments/switching-gce-nodepool/chaostoolkit-run.gif)

## Extending the Chaos Toolkit

The Chaos Toolkit plays the experiment description that you provide to it. Experiments are made up of probes 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.

In terms of implementation, the [Chaos Toolkit currently supports][extend] 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][api] you can then specify your own unique extensions in your experiment definitions.

The core implementation of the Chaos Toolkit API can be found in the [chaostoolkit-lib][chaoslib] project.

[extend]: http://chaostoolkit.org/reference/extending/approaches/ [chaoslib]: https://github.com/chaostoolkit/chaostoolkit-lib

### Current Known Extensions

The following free and open source extensions are available for your probes and/or actions:

  • [chaostoolkit-kubernetes][chaoskube]: Kubernetes activities

  • [chaostoolkit-gremlin][chaosgremlin]: Gremlin, Inc activities

  • [chaostoolkit-aws][chaosaws]: AWS activities

  • [chaostoolkit-google-cloud][chaosgce]: Google Cloud Engine activities

  • [chaostoolkit-azure][chaosazure]: Microsoft Azure activities

  • [chaostoolkit-cloud-foundry][chaoscf]: Cloud Foundry activities

  • [chaostoolkit-prometheus][chaosprom]: Prometheus probes

  • [chaostoolkit-slack][chaosslack]: Slack notifications

  • [chaostoolkit-humio][chaoshumio]: Humio logging

[chaoskube]: https://github.com/chaostoolkit/chaostoolkit-kubernetes-support [chaosgremlin]: https://github.com/chaostoolkit-incubator/chaostoolkit-gremlin [chaosaws]: https://github.com/chaostoolkit-incubator/chaostoolkit-aws [chaosazure]: https://github.com/chaostoolkit-incubator/chaostoolkit-azure [chaosgce]: https://github.com/chaostoolkit-incubator/chaostoolkit-google-cloud [chaosprom]: https://github.com/chaostoolkit-incubator/chaostoolkit-prometheus [chaoscf]: https://github.com/chaostoolkit-incubator/chaostoolkit-cloud-foundry [chaosslack]: https://github.com/chaostoolkit-incubator/chaostoolkit-slack [chaoshumio]: https://github.com/chaostoolkit-incubator/chaostoolkit-humio

## Get involved!

Chaos Toolkit’s mission is to provide an open API to chaos engineering in all its forms. As such, we encourage and welcome you to [join][join] our open community Slack team to discuss and share your experiments and needs with the community.

[join]: https://join.chaostoolkit.org/

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 contact@chaostoolkit.org with any questions as well.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

chaostoolkit-0.15.0.tar.gz (17.6 kB view details)

Uploaded Source

Built Distribution

chaostoolkit-0.15.0-py3-none-any.whl (13.6 kB view details)

Uploaded Python 3

File details

Details for the file chaostoolkit-0.15.0.tar.gz.

File metadata

  • Download URL: chaostoolkit-0.15.0.tar.gz
  • Upload date:
  • Size: 17.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/38.5.1 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.5

File hashes

Hashes for chaostoolkit-0.15.0.tar.gz
Algorithm Hash digest
SHA256 32242f34a4eaf2dc3e7af0ab1e3a61977b2cd70b6520970d86b171c3608c39cf
MD5 2f1f75fa1a0675e17a02b34b7dde97db
BLAKE2b-256 3d25a3ee6bf139a0f80e5b6e25776da7e1d66e620eb6f5e0c77d5c7703b46b27

See more details on using hashes here.

File details

Details for the file chaostoolkit-0.15.0-py3-none-any.whl.

File metadata

  • Download URL: chaostoolkit-0.15.0-py3-none-any.whl
  • Upload date:
  • Size: 13.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/38.5.1 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.5

File hashes

Hashes for chaostoolkit-0.15.0-py3-none-any.whl
Algorithm Hash digest
SHA256 83db83a6e4d0e1983c0f75af02d99c018c2cec17142ff6bda62bc9330672a8fc
MD5 ed10b9a68a75f22cf5c3158883590a36
BLAKE2b-256 0a83441c58c556324d0c06b7089f708853c692ebe8ec27b09aff3ff85c810110

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page