Skip to main content

Chaos Toolkit Reporting

Project description

A general purpose reporting generator for Chaos Toolkit

Build, Test, and Lint

The Chaos Toolkit reporting extension library.

Purpose

The purpose of this library is to provide reporting support to the Chaos Toolkit experiment results.

Features

The library takes the journal generated by the chaos run command and transforms into a human friendly report. The report can be a standalone PDF or HTML document.

Install

Install this package as any other Python packages:

$ pip install -U chaostoolkit-reporting

Notice that this draws a few dependencies:

Some of them are LGPL v3 licensed.

You will also need to install some additional dependencies that the chaos report command relies upon.

Usage

Once installed, a new report subcommand will be made available to the chaos command, use it as follows:

$ chaos report --export-format=html5 journal.json report.html

or, for a PDF document:

$ chaos report --export-format=pdf journal.json report.pdf

You can also generate a single report from many journals at once:

$ chaos report --export-format=pdf journal-1.json journal-2 journal-3 report.pdf

Or more succinctly:

$ chaos report --export-format=pdf journal-*.json report.pdf

Download a Docker Image

As the dependencies for this plugin can be difficult to get right, we also provide a docker image - note that this image is rather big with 1.4Gb to pull. You can install Docker from the Docker Hub.

$ docker pull chaostoolkit/reporting

Use a Docker container

To generate a PDF report using the Docker image you must first ensure that you are running the command from where the journal.json file, generated during an experiment run, can be found. To check for this you can run:

$ ls

And you should see the journal.json file:

journal.json

Now you can run the docker command:

$ docker run \
    --user `id -u` \
    -v `pwd`:/tmp/result \
    -it \
    chaostoolkit/reporting

This will create chaostoolkit.log and report.pdf files in this directory.

$ ls
chaostoolkit.log   journal.json   report.pdf

The report.json file will be owned by the user id returned by the command id -u, it should be your user. The reason we specify a user is that, by default, the container runs as root and the image doesn't make a guess about which user will run the container. If you don't have the id command you can set the value manually as follows instead: --user 1000:1000 assuming both your user and group ids are 1000.

The default command of the image is equivalent to running this without a container:

$ chaos report --export-format=pdf journal.json report.pdf

If you wish to override that command, pass the chaos report parameters as follows:

$ docker run \
    --user `id -u` \
    -v `pwd`:/tmp/result \
    -it \
    chaostoolkit/reporting -- report --export-format=html5 journal.json report.html

And the same files will be created:

$ ls
chaostoolkit.log   journal.json   report.pdf

Contribute

Contributors to this project are welcome as this is an open-source effort that seeks discussions and continuous improvement.

From a code perspective, if you wish to contribute, you will need to run a Python 3.7+ environment. Then, fork this repository and submit a PR. The project cares for code readability and checks the code style to match best practices defined in PEP8. Please also make sure you provide tests whenever you submit a PR so we keep the code reliable.

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_reporting-0.18.0.tar.gz (26.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

chaostoolkit_reporting-0.18.0-py3-none-any.whl (29.4 kB view details)

Uploaded Python 3

File details

Details for the file chaostoolkit_reporting-0.18.0.tar.gz.

File metadata

  • Download URL: chaostoolkit_reporting-0.18.0.tar.gz
  • Upload date:
  • Size: 26.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/5.1.1 CPython/3.12.7

File hashes

Hashes for chaostoolkit_reporting-0.18.0.tar.gz
Algorithm Hash digest
SHA256 f3f2f5980d53ac7b22e781255a030f20d28fee4f80bff9e8978a67753c5bafba
MD5 d4d1f420f7e0ad4d6b3c7206346bff22
BLAKE2b-256 f4107e0556fd7c863b8543d47a39b11aeafa1feafd3376822f18f25cb99114ff

See more details on using hashes here.

Provenance

The following attestation bundles were made for chaostoolkit_reporting-0.18.0.tar.gz:

Publisher: release.yaml on chaostoolkit/chaostoolkit-reporting

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file chaostoolkit_reporting-0.18.0-py3-none-any.whl.

File metadata

File hashes

Hashes for chaostoolkit_reporting-0.18.0-py3-none-any.whl
Algorithm Hash digest
SHA256 c80ef21036e91bbba36389736b0e991e4adf5b3f123d6a4945c91d08dd4ec486
MD5 df6d59fec39350686d7e25a6ec0c7217
BLAKE2b-256 427b30d346eb4cce9bdfaf37f9a4caed1bf68cbeb1f0a589b4fccb81c14e4d56

See more details on using hashes here.

Provenance

The following attestation bundles were made for chaostoolkit_reporting-0.18.0-py3-none-any.whl:

Publisher: release.yaml on chaostoolkit/chaostoolkit-reporting

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

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