Creating a Multi-Experiment Report
Understand how to execute multiple chaos experiments in Kubernetes, save their results in separate journal files, and combine these for a consolidated multi-experiment report. Discover how this practice enhances application and cluster reliability by providing complete insights into system behavior under various failure scenarios.
Assuming that we want to see how we can generate reports based on multiple experiments, the first thing we need to do is to run a second experiment. Otherwise, we’d be left with data (journal) from a single experiment.
So, we are going to execute yet another experiment that will generate a second journal file. After that, we’ll try to figure out how to create a report based on both journals.
Using the definition of network-delay.yaml
Let’s start by taking a quick look at yet another definition.
The output is as follows.
version: 1.0.0
title: What happens if we abort and delay responses
description: If responses are aborted and delayed, the dependant application should retry and/or timeout requests
tags:
- k8s
- istio
- http
configuration:
ingress_host:
type: env
key: INGRESS_HOST
steady-state-hypothesis:
title: The app is healthy
probes:
- type: probe
name: app-responds-to-requests
tolerance: 200
provider:
type: http
timeout: 15
verify_tls: false
url: http://${ingress_host}?addr=http://go-demo-8
headers:
...