Index

A

• actions, Exploring and Discovering Evidence of Weaknesses
  • drain_nodes action in chaos experiment, Using the Kubernetes Driver from Your Method
  • implemented in Python drivers for Chaos Toolkit, probes versus, Creating Your Own Custom Chaos Driver in Python
  • implementing through process calls, Implementing Probes and Actions Through Process Calls
  • implementing with HTTP calls, Implementing Probes and Actions with HTTP Calls
• activities, Adding Your (Very) Simple Human Interaction Control, Discovering What’s Possible with the chaos discover Command
  • Activity type, Adding Your (Very) Simple Human Interaction Control
  • each activity subjected to a control, Adding Your (Very) Simple Human Interaction Control
  • skipping or executing in an experiment, Skipping or Executing an Experiment’s Activity-Summary
• app-must-respond probe, Moving Values into Configuration
• application-endpoint configuration property, Moving Values into Configuration
  • specifying as environment variable, Specifying Configuration Properties as Environment Variables
• applications, Chaos Engineering from Beginning to End
  • single service, replicated three times, The Application: A Single Service, Replicated Three Times
  • sketches for, Sketching Your System
• approvals, getting for Game Day, Get Approval!
• arguments, specifying for process calls, Implementing Probes and Actions Through Process Calls
• automated chaos engineering
  • tooling up for, Getting Tooled Up for Automated Chaos Engineering-Summary
    • Chaos Toolkit, Getting Tooled Up for Automated Chaos Engineering
    • installing Chaos Toolkit CLI, Installing the Chaos Toolkit CLI
    • installing Python 3, Installing Python 3
• availability, Creating Your Hypothesis Backlog

B

• blast radius, Sandbox/Staging or Production?
  • in first example Chaos Toolkit experiment, Exploring and Discovering Evidence of Weaknesses
  • for Game Day, Decide Where

C

• chaos command, Getting Tooled Up for Automated Chaos Engineering
  • chaos --help, Installing the Chaos Toolkit CLI
  • chaos discover, Installing the Chaos Toolkit CLI, Discovering What’s Possible with the chaos discover Command
  • chaos init, Installing the Chaos Toolkit CLI, Authoring a New Experiment with the chaos init Command
  • chaos report, Creating a Single-Experiment Execution Report, Extending the Chaos Commands with Plug-ins
  • chaos run, Installing the Chaos Toolkit CLI, Running Your Experiment
    • adding to script to execute chaos tests, Creating a Script to Execute Your Chaos Tests
  • chaos validate, Checking Your Experiment with the chaos validate Command
  • default, The Default Chaos Commands
• chaos engineering
  • about, Chaos Engineering Distilled
  • addressing the whole sociotechnical system, Chaos Engineering Addresses the Whole Sociotechnical System
  • chaos engineers, Is There a “Chaos Engineer”?
  • defined, Chaos Engineering Defined
  • how not to do, Building a Hypothesis Backlog
  • journey through entire cycle, Chaos Engineering from Beginning to End-Summary
    • defining the steady-state hypothesis, Defining Your Steady-State Hypothesis
    • injecting turbulent conditions in experiment, Injecting Turbulent Conditions in an Experiment’s Method-Using the Kubernetes Driver from Your Method
    • naming the experiment, Naming Your Experiment
    • rollbacks, Being a Good Citizen with Rollbacks
    • running experiment on Kubernetes cluster, Bringing It All Together and Running Your Experiment-Overcoming a Weakness: Applying a Disruption Budget
    • target system, The Target System-Hunting for a Weakness
  • and observability, Chaos Engineering and Observability
  • practices of, The Practices of Chaos Engineering
    • experimenting in sandbox/staging or production, Sandbox/Staging or Production?
  • process of, The Process of Chaos Engineering
• chaos engineering learning loop
  • discovery and analysis phase, Running Your Experiment
  • exploring target system for weaknesses, Exploring and Discovering Evidence of Weaknesses
• chaos experiments (see experiments)
• Chaos Monkey for Spring Boot, Creating Your Own Custom Chaos Driver in Python
  • invoking the API, Adding the Probe
• Chaos Monkey, unchained in production, Building a Hypothesis Backlog
• chaos tests (see testing)
• Chaos Toolkit, Getting Tooled Up for Automated Chaos Engineering, Chaos Toolkit Reference-Extending the Chaos Commands with Plug-ins
  • authoring new experiment with chaos init, Authoring a New Experiment with the chaos init Command
  • checking experiment with chaos validate, Checking Your Experiment with the chaos validate Command
  • Control concept, Bringing It All Together and Running Your Experiment
  • control function implementation, hooking into experiment life cycle, Adding Logging to Your Chaos Experiments
  • controls, Enabling Controls, Human Intervention in Chaos Experiment Automation
  • creating new extension for controls, Creating a New Chaos Toolkit Extension for Your Controls
  • default chaos commands, The Default Chaos Commands
  • discovering what's possible with chaos discover, Discovering What’s Possible with the chaos discover Command
  • experiment specification, Exploring and Discovering Evidence of Weaknesses
  • extending chaos commands with plug-ins, Extending the Chaos Commands with Plug-ins
  • extensibility, Creating Custom Chaos Drivers
  • extensions, Using the Kubernetes Driver from Your Method
  • how it interprets and executes an experiment, Under the Skin of chaos run
  • installing, Getting Tooled Up for Automated Chaos Engineering
  • installing chaos command, Installing the Chaos Toolkit CLI
  • installing CLI for, Installing the Chaos Toolkit CLI
  • installing Python 3 for, Installing Python 3
  • Kubernetes driver, installing, Installing the Chaos Toolkit Kubernetes Driver
  • .log and journal.json files, Validating the Improvement
  • OpenTracing extension, Introducing OpenTracing
  • workflow, Installing the Chaos Toolkit CLI
• Chaos Toolkit community, Sketching Your System
• Chaos Toolkit Community Playground, The Chaos Toolkit Community Playground
• chaostoolkit-incubator/community-playground repo, Setting Up the Sample Target System
• chaostoolkit-reporting plug-in, Creating a Single-Experiment Execution Report
• circuit breakers, Chaos Engineering Defined
• click library, Adding Your (Very) Simple Human Interaction Control
  • confirm function, Skipping or Executing an Experiment’s Activity
• cluster administrators, The People: Application Team and Cluster Administrators
• collaboration in chaos engineering, Collaborative Chaos-Summary
  • creating and sharing human-readable experiment reports, Creating and Sharing Human-Readable Chaos Experiment Reports-Summary
  • sharing experiment definitions, Sharing Experiment Definitions-Scoping Secrets
  • specifying contribution model, Specifying a Contribution Model
• command-line interface (CLI), Getting Tooled Up for Automated Chaos Engineering
  • (see also chaos command)
  • installing for Chaos Toolkit, Installing the Chaos Toolkit CLI
• Community Playground project, Sketching Your System
• configuration
  • configuration block in Chaos Toolkit Instana experiment, Scoping Secrets
  • embedded, in chaos experiment, Sharing Experiment Definitions
  • externalizing, Sharing Experiment Definitions
  • moving values into, Moving Values into Configuration
  • for OpenTracing control, Applying the OpenTracing Control
  • in probe function, Adding the Probe
  • specifying configuration properties as environment variables, Moving Values into Configuration
• continuous chaos, Continuous Chaos-Summary
  • defined, What Is Continuous Chaos?
  • scheduling through continuous delivery pipeline using Jenkins, Scheduling Continuous Chaos with Jenkins
    • adding chaos tests to Jenkins build, Adding Your Chaos Tests to a Jenkins Build-Adding Your Chaos Tests to a Jenkins Build
    • getting Jenkins, Grabbing a Copy of Jenkins
    • scheduling chaos tests using build triggers, Scheduling Your Chaos Tests in Jenkins with Build Triggers
  • scheduling using cron, Scheduling Continuous Chaos Using cron-Adding Your Chaos Tests Script to cron
    • adding chaos test execution script to cron, Adding Your Chaos Tests Script to cron
    • creating script to execute chaos tests, Creating a Script to Execute Your Chaos Tests-Adding Your Chaos Tests Script to cron
• continuous delivery pipeline, Scheduling Continuous Chaos with Jenkins
• contributions
  • contribution model, Continuous Chaos
  • reports on, Creating and Sharing a Multiple Experiment Execution Report
  • specifying contribution model, Specifying a Contribution Model
• controls, Experiment “Controls”-Experiment “Controls”, Implementing Chaos Engineering Observability
  • abort human interaction control, Skipping or Executing an Experiment’s Activity
  • for automated chaos experiments, Chaos and Operations
  • custom, Creating Custom Chaos Drivers
  • enabling, Enabling Controls
    • globally, Adding Your (Very) Simple Human Interaction Control
    • inline, in an experiment, Enabling a Control Inline in an Experiment
  • for human intervention in automated chaos experiments, Human Intervention in Chaos Experiment Automation-Summary
    • adding simple control, Adding Your (Very) Simple Human Interaction Control-Adding Your (Very) Simple Human Interaction Control
    • creating new Chaos Toolkit extension for, Creating a New Chaos Toolkit Extension for Your Controls
    • skipping or executing experiment's activity, Skipping or Executing an Experiment’s Activity-Summary
  • OpenTracing control, applying, Applying the OpenTracing Control
  • pushing tracing info to distributed dashboards, Tracing Your Chaos Experiments
• Cookiecutter template (Python), Creating a New Python Module for Your Chaos Toolkit Extension Project, Creating a New Chaos Toolkit Extension for Your Controls
• cron
  • adding chaos test script to, Adding Your Chaos Tests Script to cron
  • scheduling chaos tests with, Scheduling Your Chaos Tests in Jenkins with Build Triggers

D

• dark debt, Chaos Engineering Defined
  • locations of, Locations of Dark Debt
  • sketches for potential areas of, Sketching Your System
• dashboards, Chaos and Operations
  • for tracing information, Applying the OpenTracing Control
• DELETE HTTP requests, Implementing Probes and Actions with HTTP Calls
• delivery pipeline, chaos experiments in, Scheduling Continuous Chaos with Jenkins
• dependencies
  • installing for human interaction control, Adding Your (Very) Simple Human Interaction Control
  • Python, controlling in virtual environment, Installing the Chaos Toolkit CLI
• discovery and analysis phase, chaos engineering learning loop, Running Your Experiment
• Disruption Budget (Kubernetes), Overcoming a Weakness: Applying a Disruption Budget
• Docker
  • making sure it's installed on your system, Creating a Single-Experiment Execution Report
  • prepackaged container of Chaos Toolkit, Creating a Single-Experiment Execution Report
• docker command, producing PDF report, Creating a Single-Experiment Execution Report
• drivers, Installing the Chaos Toolkit Kubernetes Driver
  • custom chaos drivers, creating, Creating Custom Chaos Drivers-Summary
    • creating Python module for Chaos Toolkit extension, Creating a New Python Module for Your Chaos Toolkit Extension Project-Summary
    • in Python, Creating Your Own Custom Chaos Driver in Python-Creating Your Own Custom Chaos Driver in Python
    • without custom code, Creating Your Own Custom Driver with No Custom Code-Implementing Probes and Actions Through Process Calls
  • Instana Chaos Toolkit, Sharing Experiment Definitions
• Dungeons & Dragons Game Day style, Pick a Style of Game Day
• durability, Creating Your Hypothesis Backlog

E

• editable with no version control message (pip), Adding Your (Very) Simple Human Interaction Control
• environment variables
  • secrets sourced as, Externalizing Secrets
  • specifying configuration properties as, Moving Values into Configuration
• experiments
  • automated chaos experiments, operational concerns, Chaos and Operations
  • chaos tests vs. chaos experiments, Continuous Chaos
  • collaborative, Collaborative Chaos
    • sharing experiment definitions, Sharing Experiment Definitions-Scoping Secrets
  • constructing Game Day experiment, Describe Your Game Day Experiment
  • controls for automated chaos experiments, Experiment “Controls”-Experiment “Controls”
    • enabling, Enabling Controls
  • defining your steady-state hypothesis, Defining Your Steady-State Hypothesis
  • executing in sandbox/staging or production, Sandbox/Staging or Production?
  • formats for, specifying in YAML or JSON, Getting Tooled Up for Automated Chaos Engineering
  • injecting turbulent conditions in the method, Injecting Turbulent Conditions in an Experiment’s Method-Using the Kubernetes Driver from Your Method
  • naming, Naming Your Experiment
  • rollbacks in experiment on Kubernetes cluster, Being a Good Citizen with Rollbacks
  • running experiment on Kubernetes cluster, Bringing It All Together and Running Your Experiment-Overcoming a Weakness: Applying a Disruption Budget
  • running in safer environment, Decide Where
  • starting with, Start with Experiments?
  • stopping a running chaos experiment, Bringing It All Together and Running Your Experiment
  • writing and running chaos experiment, Writing and Running Your First Automated Chaos Experiment-Summary
    • Chaos Toolkit experiment specification, Exploring and Discovering Evidence of Weaknesses
    • how Chaos Toolkit executes an experiment, Under the Skin of chaos run
    • improving the target system, Improving the System-Improving the System
    • indication of need for improvement, Steady-State Deviation Might Indicate “Opportunity for Improvement”
    • method of the experiment, Exploring and Discovering Evidence of Weaknesses
    • running your experiment, Running Your Experiment-Running Your Experiment
    • setting up sample target system, Setting Up the Sample Target System-A Quick Tour of the Sample System
    • validating improvement to target system, Validating the Improvement-Summary

F

• FailedActivity exception, Adding the Probe
• failure cards, Capturing “What Could Possibly Go Wrong?”
• Failure Mode and Effects Analysis, Introducing Likelihood and Impact
• failures
  • acceptable, Adding What You Care About
  • affecting what you care about most, Building a Likelihood-Impact Map
  • broad areas of, Locations of Dark Debt
  • deciding what could go wrong, Capturing “What Could Possibly Go Wrong?”
  • heroes as single points of, Consider a “Safety Monitor”
  • likelihood and impact of, Introducing Likelihood and Impact
  • making hypotheses from, Creating Your Hypothesis Backlog

G

• Game Days
  • planning and running, Planning and Running a Manual Game Day-Summary
    • case of the lucky game day facilitator, Consider a “Safety Monitor”
    • deciding when and for how long, Decide When and For How Long
    • deciding where, Decide Where
    • deciding who participates and who observes, Decide Who Participates and Who Observes
    • getting approval, Get Approval!
    • goals and objectives of Game Day, What Is a Game Day?
    • picking a hypothesis, Pick a Hypothesis
    • picking a style for Game Day, Pick a Style of Game Day
    • planning, steps in, Planning Your Game Day
    • running, Running the Game Day
    • safety monitor, considering, Consider a “Safety Monitor”
  • running in safer environment, Sandbox/Staging or Production?
  • safety and, Chaos and Operations
• GET HTTP requests, Implementing Probes and Actions with HTTP Calls

H

• headers (HTTP), Implementing Probes and Actions with HTTP Calls
• help (chaos command), Installing the Chaos Toolkit CLI
• heroes, Consider a “Safety Monitor”
• HTTP calls, implementing probes and actions, Implementing Probes and Actions with HTTP Calls
• human intervention in automated chaos experiments, Human Intervention in Chaos Experiment Automation-Summary
  • creating new Chaos Toolkit extension for controls, Creating a New Chaos Toolkit Extension for Your Controls
  • simple human interaction control, adding, Adding Your (Very) Simple Human Interaction Control-Adding Your (Very) Simple Human Interaction Control
  • skipping or executing experiment's activity, Skipping or Executing an Experiment’s Activity-Summary
• human intervention, continuous chaos and, What Is Continuous Chaos?
• Humio extension, Adding Logging to Your Chaos Experiments
• hypotheses
  • creating hypothesis backlog, Creating Your Hypothesis Backlog
  • gathering, Gathering Hypotheses
    • decididng what could go wrong in the system, Capturing “What Could Possibly Go Wrong?”
    • from incident analysis, Incident Analysis
    • sketching your system, Sketching Your System
  • picking for Game Day experiment, Pick a Hypothesis
  • steady-state, Describe Your Game Day Experiment

I

• impact, Capturing “What Could Possibly Go Wrong?”
  • building likelihood-impact map, Introducing Likelihood and Impact
  • of turbulent conditions evolving on Game Day, Pick a Hypothesis
• incident analysis, Incident Analysis
• Informed in Advance style for Game Days, Pick a Style of Game Day
• infrastructure, Chaos Engineering from Beginning to End
  • dark debt in, Locations of Dark Debt
  • provided by Kubernetes in three-node cluster, The Platform: A Three-Node Kubernetes Cluster
  • sketches for, Sketching Your System
• Instana experiment, Sharing Experiment Definitions
  • Instana Chaos Toolkit driver code, Sharing Experiment Definitions
• instana_api_token secret, sourcing as environment variable, Externalizing Secrets
• instana_host configuration property, Moving Values into Configuration
  • specifying as environment variable, Specifying Configuration Properties as Environment Variables
• InterruptException, Skipping or Executing an Experiment’s Activity

J

• Jaeger tracing visualization dashboard, Applying the OpenTracing Control
• Jenkins, Scheduling Continuous Chaos with Jenkins
  • adding chaos tests to Jenkins build, Adding Your Chaos Tests to a Jenkins Build-Adding Your Chaos Tests to a Jenkins Build
  • getting a copy of, Grabbing a Copy of Jenkins
  • scheduling chaos tests with build triggers, Scheduling Your Chaos Tests in Jenkins with Build Triggers
• journal.json file (Chaos Toolkit), Validating the Improvement
• JSON, specifying chaos experiments in, Getting Tooled Up for Automated Chaos Engineering

K

• knowledge, heroes as single points of, Consider a “Safety Monitor”
• kubectl apply command, Bringing It All Together and Running Your Experiment, Overcoming a Weakness: Applying a Disruption Budget
• Kubernetes
  • Disruption Budget, applying, Overcoming a Weakness: Applying a Disruption Budget
  • installing Chaos Toolkit Kubernetes driver, Installing the Chaos Toolkit Kubernetes Driver
  • rollback of removal of node in experiment, Being a Good Citizen with Rollbacks
  • three-node cluster platform, The Platform: A Three-Node Kubernetes Cluster
  • using driver from experiment's method, Using the Kubernetes Driver from Your Method

L

• likelihood
  • building likelihood-impact map for failures, Introducing Likelihood and Impact
  • of turbulent conditions evolving on Game Day, Pick a Hypothesis
• logging
  • adding to chaos experiments, Adding Logging to Your Chaos Experiments-Tracing Your Chaos Experiments
    • centralized chaos logging in action, Centralized Chaos Logging in Action
  • centralized, Chaos and Operations
  • chaostoolkit.log file, Validating the Improvement

M

• measurements of system working in expected way, Describe Your Game Day Experiment
• mental models of the system, refining, Sketching Your System
• method
  • creating method block for an experiment, Using the Kubernetes Driver from Your Method
  • of first Chaos Toolkit chaos experiment, Exploring and Discovering Evidence of Weaknesses
  • for Game Day experiment, Describe Your Game Day Experiment

N

• normal and healthy behavior for target system, Exploring and Discovering Evidence of Weaknesses, Defining Your Steady-State Hypothesis

O

• observability, Sharing Experiment Definitions, Implementing Chaos Engineering Observability-Summary
  • adding logging to chaos experiments, Adding Logging to Your Chaos Experiments-Tracing Your Chaos Experiments
  • chaos engineering and, Chaos Engineering and Observability
  • tracing chaos experiments, Tracing Your Chaos Experiments-Summary
• observation, Chaos and Operations
• observers, deciding for Game Day, Decide Who Participates and Who Observes
• OpenTracing, Introducing OpenTracing
• operations, chaos and, Chaos and Operations-Summary
  • enabling controls, Enabling Controls
    • globally, Enabling a Control Globally
    • inline, in an experiment, Enabling a Control Inline in an Experiment
  • experiment controls, Experiment “Controls”-Experiment “Controls”
  • operational concerns with automated chaos experiments, Chaos and Operations
• optimism, group bias toward, Building a Likelihood-Impact Map

P

• participants, deciding for Game Day, Decide Who Participates and Who Observes
• paths (for process calls), Implementing Probes and Actions Through Process Calls
• people, practices, and processes, Chaos Engineering from Beginning to End
  • dark debt in, Locations of Dark Debt
  • people, application team and administration, The People: Application Team and Cluster Administrators
    • potential conflict in goals, Hunting for a Weakness
  • sketches for, Sketching Your System
• pessimism, group bias toward, Building a Likelihood-Impact Map
• pip
  • Editable with no version control, Adding Your (Very) Simple Human Interaction Control
  • installing Chaos Toolkit Kubernetes driver, Installing the Chaos Toolkit Kubernetes Driver
  • installing Chaos Toolkit with, Installing the Chaos Toolkit CLI
  • installing human interaction control project as Python module, Adding Your (Very) Simple Human Interaction Control
  • pip freeze command, Adding Your (Very) Simple Human Interaction Control
• platforms, Chaos Engineering from Beginning to End
  • dark debt in, Locations of Dark Debt
  • sketches for, Sketching Your System
  • three-node Kubernetes cluster, The Platform: A Three-Node Kubernetes Cluster
• plug-ins, extending chaos commands with, Extending the Chaos Commands with Plug-ins
• POST HTTP requests, Implementing Probes and Actions with HTTP Calls
• probes
  • adding to new Python module for Chaos Toolkit extension, Adding the Probe
  • implemented in Python drivers for Chaos Toolkit, actions versus, Creating Your Own Custom Chaos Driver in Python
  • implementing through process calls, Implementing Probes and Actions Through Process Calls
  • implementing with HTTP calls, Implementing Probes and Actions with HTTP Calls
• process providers, Implementing Probes and Actions with HTTP Calls
  • power of, Implementing Probes and Actions Through Process Calls
• production systems
  • failure in, Chaos Engineering Addresses the Whole Sociotechnical System
  • hostile properties of, Chaos Engineering Addresses the Whole Sociotechnical System
• production, deciding whether to experiment in, Sandbox/Staging or Production?
• providers
  • HTTP type, Implementing Probes and Actions with HTTP Calls
  • process, Implementing Probes and Actions with HTTP Calls
  • secrets property on, Scoping Secrets
• pytest command, Adding the Probe
• Python
  • Chaos Toolkit extensions and, Using the Kubernetes Driver from Your Method
  • creating custom chaos driver in, Creating Your Own Custom Chaos Driver in Python-Creating Your Own Custom Chaos Driver in Python
  • creating new Chaos Toolkit extension module for controls, Creating a New Chaos Toolkit Extension for Your Controls
  • creating new module for Chaos Toolkit extension project, Creating a New Python Module for Your Chaos Toolkit Extension Project-Summary
  • creating virtual environment for Chaos Toolkit and dependencies, Installing the Chaos Toolkit CLI
  • drain_nodes function in module, Using the Kubernetes Driver from Your Method
  • human interaction control, Adding Your (Very) Simple Human Interaction Control
  • implementation of Chaos Toolkit controls, Experiment “Controls”
  • installing Python 3, Installing Python 3
  • probe using call to Python module, Defining Your Steady-State Hypothesis

R

• reliability, Chaos Engineering Defined
• remediating actions, Being a Good Citizen with Rollbacks
  • (see also rollbacks)
• replicas directive, The Application: A Single Service, Replicated Three Times
• reports
  • for Chaos Toolkit experiments, Installing the Chaos Toolkit CLI
  • chaos report implementation, Extending the Chaos Commands with Plug-ins
  • creating and sharing chaos experiment reports, Creating and Sharing Human-Readable Chaos Experiment Reports-Summary
    • creating multiple experiment execution report, Creating and Sharing a Multiple Experiment Execution Report
    • creating single experiment execution report, Creating a Single-Experiment Execution Report
• requirements-dev.txt file, Adding Your (Very) Simple Human Interaction Control
• resilience
  • areas of attack on, Chaos Engineering from Beginning to End
  • lack of, surfaced by first chaos experiment, Steady-State Deviation Might Indicate “Opportunity for Improvement”
• retrospectives, holding Game Day just before, Decide When and For How Long
• rollbacks
  • activities in, always executed, Skipping or Executing an Experiment’s Activity
  • in experiment on Kubernetes cluster, Being a Good Citizen with Rollbacks
  • remediating actions following Game Day experiment, Describe Your Game Day Experiment

S

• safety monitor for Game Days, Consider a “Safety Monitor”
  • importance of, Consider a “Safety Monitor”
• sandbox/staging, executing experiments in, Sandbox/Staging or Production?
• secrets
  • embedded, in chaos experiment, Sharing Experiment Definitions
  • externalizing, Sharing Experiment Definitions, Externalizing Secrets
  • in probe function, Adding the Probe
  • scoping in Chaos Toolkit experiment, Scoping Secrets
• service level objectives (SLOs), Creating Your Hypothesis Backlog, Describe Your Game Day Experiment
• status (HTTP), Implementing Probes and Actions with HTTP Calls
• steady-state hypothesis, Describe Your Game Day Experiment
  • captured in Chaos Toolkit experiment, Exploring and Discovering Evidence of Weaknesses
  • defining for second chaos experiment, Defining Your Steady-State Hypothesis
  • deviation from, indicating need for improvement, Steady-State Deviation Might Indicate “Opportunity for Improvement”
  • use in first chaos experiment, Under the Skin of chaos run
• styles and formats for Game Days, Pick a Style of Game Day
• systems
  • deciding what could go wrong, Capturing “What Could Possibly Go Wrong?”
  • improving target system after chaos experiment, Improving the System-Improving the System
  • setting up sample target system for experiment, Setting Up the Sample Target System
  • sketching your system, Sketching Your System
  • system information with chaos discover, Discovering What’s Possible with the chaos discover Command
  • target system for second chaos experiment, The Target System-Hunting for a Weakness
    • application, single service replicated three times, The Application: A Single Service, Replicated Three Times
    • people, application team and administration, The People: Application Team and Cluster Administrators
    • platform, three-node Kubernetes cluster, The Platform: A Three-Node Kubernetes Cluster
  • tour of sample target system for experiment, A Quick Tour of the Sample System-A Quick Tour of the Sample System
  • validating improvement to target system, Validating the Improvement-Summary

T

• testing
  • chaos tests as validation of overcoming weaknesses, Continuous Chaos
  • chaos tests enabling potential for continuous chaos, What Is Continuous Chaos?
  • creating script to execute chaos tests, Creating a Script to Execute Your Chaos Tests-Adding Your Chaos Tests Script to cron
  • probes in custom Python driver, Adding the Probe
  • scheduling continuous chaos through continuous delivery pipeline with Jenkins, Scheduling Continuous Chaos with Jenkins
    • adding chaos tests to Jenkins build, Adding Your Chaos Tests to a Jenkins Build-Adding Your Chaos Tests to a Jenkins Build
    • getting Jenkins, Grabbing a Copy of Jenkins
    • scheduling chaos tests using build triggers, Scheduling Your Chaos Tests in Jenkins with Build Triggers
  • script to run chaos tests, adding to cron, Adding Your Chaos Tests Script to cron
• tolerances
  • HTTP status codes in, Implementing Probes and Actions with HTTP Calls
  • for probes in experimental method, Exploring and Discovering Evidence of Weaknesses
• tools (chaos engineering), Getting Tooled Up for Automated Chaos Engineering
  • (see also chaos engineering; Chaos Toolkit)
  • integration of Chaos Toolkit drivers with, Creating Your Own Custom Chaos Driver in Python
• tracing chaos experiments, Tracing Your Chaos Experiments-Summary
  • applying OpenTracing control, Applying the OpenTracing Control
  • OpenTracing, Introducing OpenTracing
• trust and confidence, deciding which experiments build, Start with Experiments?
• turbulent conditions
  • actions causing on Game Day, Describe Your Game Day Experiment
  • exploration in Dungeons & Dragons-style Game Day, Pick a Style of Game Day
  • injecting in chaos experiment on Kubernetes cluster, Injecting Turbulent Conditions in an Experiment’s Method-Using the Kubernetes Driver from Your Method
  • to be evolved in Game Day, Pick a Hypothesis

V

• value of Game Day discoveries, Pick a Hypothesis
• virtual environments (Python), Installing the Chaos Toolkit CLI, Setting Up the Sample Target System, Creating Your Own Custom Chaos Driver in Python
  • checking, Installing the Chaos Toolkit CLI

W

• weaknesses
  • finding evidence of, Continuous Chaos
  • improving target system to overcome, Improving the System
  • known, exploring, Chaos Engineering Defined
  • overcoming, applying disruption budet in Kubernetes cluster, Overcoming a Weakness: Applying a Disruption Budget
  • overcoming, validation of, Continuous Chaos
  • potential, in second chaos experiment, Hunting for a Weakness
  • surfacing before they become critical, Chaos Engineering Distilled