> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-testing/chaoshub/enterprise-chaoshub.md).

# Enterprise ChaosHub

Explore the fault, probe, and action templates that ship with the default Enterprise ChaosHub

The **Enterprise ChaosHub** is the default ChaosHub that Harness provides at the account level. It comes pre-built with a wide catalog of ready-to-use chaos building blocks, so you can start running experiments immediately without authoring anything yourself.

It ships with three kinds of reusable templates:

* **Fault templates**: pre-built faults organized by target platform, such as Kubernetes, AWS, GCP, and Azure.
* **Probe templates**: ready-to-use validation checks for common health and status scenarios.
* **Action templates**: reusable operations, such as custom scripts, that run during an experiment.

Use the tabs below to explore each category. Select a category card to see the templates it contains, then select any template to open its full documentation.

{% tabs %}
{% tab title="Fault Templates" %}
Pre-built fault templates grouped by target platform. Select a platform to browse its faults.

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FvhciVGZWx0ywyJq6nXiG%2Fimage.png?alt=media&amp;token=11fb3fc6-e3a0-4345-a450-78347bee5fae" alt="" data-size="line"> <strong>Fault templates for AWS</strong></summary>

<table data-view="cards" data-search="true"><thead><tr><th></th><th></th><th><select multiple><option value="availability" label="availability" color="blue"></option><option value="load balancer" label="load balancer" color="blue"></option><option value="zone" label="zone" color="blue"></option><option value="blackhole" label="blackhole" color="blue"></option><option value="vpc" label="vpc" color="blue"></option><option value="route tables" label="route tables" color="blue"></option><option value="replication" label="replication" color="blue"></option><option value="pause" label="pause" color="blue"></option><option value="dynamodb" label="dynamodb" color="blue"></option><option value="loss" label="loss" color="blue"></option><option value="id" label="id" color="blue"></option><option value="tag" label="tag" color="blue"></option><option value="cpu" label="cpu" color="blue"></option><option value="stress" label="stress" color="blue"></option><option value="dns" label="dns" color="blue"></option><option value="http" label="http" color="blue"></option><option value="latency" label="latency" color="blue"></option><option value="modify" label="modify" color="blue"></option><option value="body" label="body" color="blue"></option><option value="header" label="header" color="blue"></option><option value="reset" label="reset" color="blue"></option><option value="peer" label="peer" color="blue"></option><option value="status" label="status" color="blue"></option><option value="code" label="code" color="blue"></option><option value="io" label="io" color="blue"></option><option value="memory" label="memory" color="blue"></option><option value="network" label="network" color="blue"></option><option value="process" label="process" color="blue"></option><option value="kill" label="kill" color="blue"></option><option value="stop" label="stop" color="blue"></option><option value="agent" label="agent" color="blue"></option><option value="container" label="container" color="blue"></option><option value="volume" label="volume" color="blue"></option><option value="detach" label="detach" color="blue"></option><option value="fargate" label="fargate" color="blue"></option><option value="instance" label="instance" color="blue"></option><option value="invalid" label="invalid" color="blue"></option><option value="image" label="image" color="blue"></option><option value="restrict" label="restrict" color="blue"></option><option value="task" label="task" color="blue"></option><option value="scale" label="scale" color="blue"></option><option value="update" label="update" color="blue"></option><option value="resource" label="resource" color="blue"></option><option value="timeout" label="timeout" color="blue"></option><option value="role" label="role" color="blue"></option><option value="generic" label="generic" color="blue"></option><option value="template" label="template" color="blue"></option><option value="fis" label="fis" color="blue"></option><option value="lambda" label="lambda" color="blue"></option><option value="tcp" label="tcp" color="blue"></option><option value="block" label="block" color="blue"></option><option value="delete" label="delete" color="blue"></option><option value="source" label="source" color="blue"></option><option value="map" label="map" color="blue"></option><option value="concurrency" label="concurrency" color="blue"></option><option value="function" label="function" color="blue"></option><option value="toggle" label="toggle" color="blue"></option><option value="runtime" label="runtime" color="blue"></option><option value="status code" label="status code" color="blue"></option><option value="permission" label="permission" color="blue"></option><option value="reboot" label="reboot" color="blue"></option><option value="access" label="access" color="blue"></option><option value="ssm" label="ssm" color="blue"></option><option value="windows" label="windows" color="blue"></option><option value="ec2" label="ec2" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>ALB AZ down</strong></td><td>ALB AZ down detaches one or more availability zones from an Application Load Balancer for a configurable duration so you can test how clients, target groups, and AZ-aware routing behave when a zone is taken out of the load balancer rotation.</td><td><span data-option="availability">availability, </span><span data-option="load balancer">load balancer</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#alb-az-down">Chaos faults for AWS</a></td></tr><tr><td><strong>CLB AZ down</strong></td><td>CLB AZ down disables one or more availability zones on a Classic Load Balancer for a configurable duration so you can test how clients and back-end instances behave when an AZ is removed from the load balancer rotation.</td><td><span data-option="availability">availability, </span><span data-option="load balancer">load balancer</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#clb-az-down">Chaos faults for AWS</a></td></tr><tr><td><strong>AZ blackhole</strong></td><td>AZ blackhole isolates network traffic in one or more AWS Availability Zones, optionally scoped to specific VPCs or subnets, for a configurable duration and restores connectivity afterwards.</td><td><span data-option="zone">zone, </span><span data-option="blackhole">blackhole</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#az-blackhole">Chaos faults for AWS</a></td></tr><tr><td><strong>VPC route misconfiguration</strong></td><td>VPC route misconfiguration temporarily removes specified CIDR routes from VPC route tables and restores them afterwards.</td><td><span data-option="vpc">vpc, </span><span data-option="route tables">route tables</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#vpc-route-misconfiguration">Chaos faults for AWS</a></td></tr><tr><td><strong>DynamoDB replication pause</strong></td><td>DynamoDB replication pause pauses cross-region replication on DynamoDB global tables using an AWS FIS experiment.</td><td><span data-option="replication">replication, </span><span data-option="pause">pause, </span><span data-option="dynamodb">dynamodb</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#dynamodb-replication-pause">Chaos faults for AWS</a></td></tr><tr><td><strong>EBS loss by ID</strong></td><td>EBS loss by ID detaches an EBS volume by volume ID for a configurable duration and reattaches it afterwards.</td><td><span data-option="loss">loss, </span><span data-option="id">id</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ebs-loss-by-id">Chaos faults for AWS</a></td></tr><tr><td><strong>EBS loss by tag</strong></td><td>EBS loss by tag detaches EBS volumes selected by tag for a configurable duration and reattaches them afterwards.</td><td><span data-option="loss">loss, </span><span data-option="tag">tag</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ebs-loss-by-tag">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 CPU hog</strong></td><td>EC2 CPU hog stresses configurable CPU cores at a configurable load percentage inside a target EC2 instance.</td><td><span data-option="cpu">cpu, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-cpu-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 DNS chaos</strong></td><td>EC2 DNS chaos fails DNS resolution for selected hostnames on a target EC2 instance.</td><td><span data-option="dns">dns</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-dns-chaos">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 HTTP latency</strong></td><td>EC2 HTTP latency adds latency to inbound HTTP traffic on a configurable target port.</td><td><span data-option="http">http, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-http-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 HTTP modify body</strong></td><td>EC2 HTTP modify body rewrites HTTP response bodies on a configurable target port.</td><td><span data-option="http">http, </span><span data-option="modify">modify, </span><span data-option="body">body</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-http-modify-body">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 HTTP modify header</strong></td><td>EC2 HTTP modify header adds, changes, or removes HTTP headers on requests or responses.</td><td><span data-option="http">http, </span><span data-option="modify">modify, </span><span data-option="header">header</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-http-modify-header">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 HTTP reset peer</strong></td><td>EC2 HTTP reset peer resets inbound TCP connections to an HTTP service.</td><td><span data-option="http">http, </span><span data-option="reset">reset, </span><span data-option="peer">peer</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-http-reset-peer">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 HTTP status code</strong></td><td>EC2 HTTP status code rewrites HTTP response status codes on a configurable target port.</td><td><span data-option="http">http, </span><span data-option="status">status, </span><span data-option="code">code</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-http-status-code">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 IO stress</strong></td><td>EC2 IO stress generates sustained filesystem read and write load on a target EC2 instance.</td><td><span data-option="io">io, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-io-stress">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 memory hog</strong></td><td>EC2 memory hog consumes a configurable amount of memory inside a target EC2 instance.</td><td><span data-option="memory">memory, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-memory-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 network latency</strong></td><td>EC2 network latency adds configurable latency and jitter to outbound target traffic.</td><td><span data-option="network">network, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-network-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 network loss</strong></td><td>EC2 network loss drops a configurable percentage of outbound target packets.</td><td><span data-option="network">network, </span><span data-option="loss">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-network-loss">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 process kill</strong></td><td>EC2 process kill kills one or more processes by PID inside a target EC2 instance.</td><td><span data-option="process">process, </span><span data-option="kill">kill</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-process-kill">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 stop by ID</strong></td><td>EC2 stop by ID stops EC2 instances by instance ID and starts them again.</td><td><span data-option="stop">stop, </span><span data-option="id">id</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-stop-by-id">Chaos faults for AWS</a></td></tr><tr><td><strong>EC2 stop by tag</strong></td><td>EC2 stop by tag stops EC2 instances selected by tag and starts them again.</td><td><span data-option="stop">stop, </span><span data-option="tag">tag</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ec2-stop-by-tag">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS agent stop</strong></td><td>ECS agent stop halts the ECS agent on EC2 container instances.</td><td><span data-option="agent">agent, </span><span data-option="stop">stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-agent-stop">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container CPU hog</strong></td><td>ECS container CPU hog stresses CPU inside containers of EC2-backed ECS tasks.</td><td><span data-option="container">container, </span><span data-option="cpu">cpu, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-cpu-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container HTTP latency</strong></td><td>ECS container HTTP latency adds latency to inbound HTTP traffic for containers in EC2-backed ECS tasks.</td><td><span data-option="container">container, </span><span data-option="http">http, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-http-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container HTTP modify body</strong></td><td>ECS container HTTP modify body rewrites HTTP response bodies for containers in EC2-backed ECS tasks.</td><td><span data-option="container">container, </span><span data-option="http">http, </span><span data-option="modify">modify, </span><span data-option="body">body</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-http-modify-body">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container HTTP reset peer</strong></td><td>ECS container HTTP reset peer resets inbound TCP connections to container HTTP services.</td><td><span data-option="container">container, </span><span data-option="http">http, </span><span data-option="reset">reset, </span><span data-option="peer">peer</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-http-reset-peer">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container HTTP status code</strong></td><td>ECS container HTTP status code rewrites HTTP response status codes for containers in EC2-backed ECS tasks.</td><td><span data-option="container">container, </span><span data-option="http">http, </span><span data-option="status">status, </span><span data-option="code">code</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-http-status-code">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container IO stress</strong></td><td>ECS container IO stress generates sustained filesystem load inside containers.</td><td><span data-option="container">container, </span><span data-option="io">io, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-io-stress">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container memory hog</strong></td><td>ECS container memory hog consumes memory inside containers of EC2-backed ECS tasks.</td><td><span data-option="container">container, </span><span data-option="memory">memory, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-memory-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container network latency</strong></td><td>ECS container network latency adds latency to outbound container traffic.</td><td><span data-option="container">container, </span><span data-option="network">network, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-network-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container network loss</strong></td><td>ECS container network loss drops a configurable percentage of outbound container packets.</td><td><span data-option="container">container, </span><span data-option="network">network, </span><span data-option="loss">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-network-loss">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS container volume detach</strong></td><td>ECS container volume detach detaches EBS volumes attached to ECS task containers.</td><td><span data-option="container">container, </span><span data-option="volume">volume, </span><span data-option="detach">detach</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-container-volume-detach">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS Fargate CPU hog</strong></td><td>ECS Fargate CPU hog stresses CPU inside a Fargate task.</td><td><span data-option="cpu">cpu, </span><span data-option="stress">stress, </span><span data-option="fargate">fargate</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-fargate-cpu-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS Fargate memory hog</strong></td><td>ECS Fargate memory hog consumes memory inside a Fargate task.</td><td><span data-option="memory">memory, </span><span data-option="stress">stress, </span><span data-option="fargate">fargate</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-fargate-memory-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS instance stop</strong></td><td>ECS instance stop stops EC2 container instances belonging to an ECS cluster.</td><td><span data-option="instance">instance, </span><span data-option="stop">stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-instance-stop">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS invalid container image</strong></td><td>ECS invalid container image swaps an ECS service container image to an invalid value.</td><td><span data-option="invalid">invalid, </span><span data-option="container">container, </span><span data-option="image">image</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-invalid-container-image">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS network restrict</strong></td><td>ECS network restrict modifies ECS service security group rules.</td><td><span data-option="network">network, </span><span data-option="restrict">restrict</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-network-restrict">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS task scale</strong></td><td>ECS task scale changes the desired count of an ECS service.</td><td><span data-option="task">task, </span><span data-option="scale">scale</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-task-scale">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS task stop</strong></td><td>ECS task stop stops ECS tasks selected by service or task ID.</td><td><span data-option="task">task, </span><span data-option="stop">stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-task-stop">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS update container resource limit</strong></td><td>ECS update container resource limit re-registers an ECS task definition with reduced CPU or memory limits.</td><td><span data-option="update">update, </span><span data-option="container">container, </span><span data-option="resource">resource</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-update-container-resource-limit">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS update container timeout</strong></td><td>ECS update container timeout modifies ECS task start and stop timeouts.</td><td><span data-option="update">update, </span><span data-option="container">container, </span><span data-option="timeout">timeout</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-update-container-timeout">Chaos faults for AWS</a></td></tr><tr><td><strong>ECS update task role</strong></td><td>ECS update task role swaps the IAM task role on an ECS service.</td><td><span data-option="task">task, </span><span data-option="role">role</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ecs-update-task-role">Chaos faults for AWS</a></td></tr><tr><td><strong>Generic experiment template</strong></td><td>Generic experiment template starts a pre-existing AWS Fault Injection Service template by ID.</td><td><span data-option="generic">generic, </span><span data-option="template">template, </span><span data-option="fis">fis</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#generic-experiment-template">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda block TCP connection</strong></td><td>Lambda block TCP connection blocks outbound TCP connections from an AWS Lambda function.</td><td><span data-option="lambda">lambda, </span><span data-option="tcp">tcp, </span><span data-option="network">network, </span><span data-option="block">block</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-block-tcp-connection">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda delete event source mapping</strong></td><td>Lambda delete event source mapping deletes Lambda event source mappings and recreates them afterwards.</td><td><span data-option="lambda">lambda, </span><span data-option="delete">delete, </span><span data-option="source">source, </span><span data-option="map">map</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-delete-event-source-mapping">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda delete function concurrency</strong></td><td>Lambda delete function concurrency removes and restores reserved concurrency configuration.</td><td><span data-option="lambda">lambda, </span><span data-option="delete">delete, </span><span data-option="concurrency">concurrency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-delete-function-concurrency">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda function layer detach</strong></td><td>Lambda function layer detach detaches and reattaches a specified Lambda layer.</td><td><span data-option="lambda">lambda, </span><span data-option="detach">detach, </span><span data-option="function">function</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-function-layer-detach">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda inject latency</strong></td><td>Lambda inject latency adds latency to every AWS Lambda invocation.</td><td><span data-option="lambda">lambda, </span><span data-option="latency">latency, </span><span data-option="network">network</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-inject-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda toggle event mapping state</strong></td><td>Lambda toggle event mapping state disables and re-enables Lambda event source mappings.</td><td><span data-option="lambda">lambda, </span><span data-option="toggle">toggle, </span><span data-option="map">map</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-toggle-event-mapping-state">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda update function memory</strong></td><td>Lambda update function memory lowers and restores Lambda memory allocation.</td><td><span data-option="lambda">lambda, </span><span data-option="function">function, </span><span data-option="memory">memory</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-update-function-memory">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda update function timeout</strong></td><td>Lambda update function timeout lowers and restores the configured Lambda timeout.</td><td><span data-option="lambda">lambda, </span><span data-option="timeout">timeout, </span><span data-option="update">update</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-update-function-timeout">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda inject status code</strong></td><td>Lambda inject status code overrides the HTTP status code returned by an AWS Lambda function.</td><td><span data-option="lambda">lambda, </span><span data-option="runtime">runtime, </span><span data-option="status code">status code</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-inject-status-code">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda update role permission</strong></td><td>Lambda update role permission detaches and reattaches an IAM policy on a Lambda execution role.</td><td><span data-option="lambda">lambda, </span><span data-option="role">role, </span><span data-option="permission">permission</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-update-role-permission">Chaos faults for AWS</a></td></tr><tr><td><strong>Lambda modify response body</strong></td><td>Lambda modify response body overrides the response body returned by an AWS Lambda function.</td><td><span data-option="lambda">lambda, </span><span data-option="runtime">runtime, </span><span data-option="function">function</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#lambda-modify-response-body">Chaos faults for AWS</a></td></tr><tr><td><strong>NLB AZ down</strong></td><td>NLB AZ down detaches availability zones from a Network Load Balancer for a configurable duration.</td><td><span data-option="load balancer">load balancer, </span><span data-option="availability">availability</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#nlb-az-down">Chaos faults for AWS</a></td></tr><tr><td><strong>RDS instance delete</strong></td><td>RDS instance delete deletes a target RDS DB instance.</td><td><span data-option="instance">instance, </span><span data-option="delete">delete</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#rds-instance-delete">Chaos faults for AWS</a></td></tr><tr><td><strong>RDS instance reboot</strong></td><td>RDS instance reboot reboots a target RDS DB instance, with optional Multi-AZ failover.</td><td><span data-option="instance">instance, </span><span data-option="reboot">reboot</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#rds-instance-reboot">Chaos faults for AWS</a></td></tr><tr><td><strong>Resource access restrict</strong></td><td>Resource access restrict temporarily strips ingress or egress rules from AWS security groups.</td><td><span data-option="resource">resource, </span><span data-option="access">access, </span><span data-option="restrict">restrict</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#resource-access-restrict">Chaos faults for AWS</a></td></tr><tr><td><strong>SSM chaos by ID</strong></td><td>SSM chaos by ID runs an arbitrary AWS Systems Manager document against an EC2 instance selected by ID.</td><td><span data-option="ssm">ssm, </span><span data-option="id">id</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ssm-chaos-by-id">Chaos faults for AWS</a></td></tr><tr><td><strong>SSM chaos by tag</strong></td><td>SSM chaos by tag runs an arbitrary AWS Systems Manager document against EC2 instances selected by tag.</td><td><span data-option="ssm">ssm, </span><span data-option="tag">tag</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#ssm-chaos-by-tag">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 blackhole chaos</strong></td><td>Windows EC2 blackhole chaos drops target network traffic on Windows EC2 instances.</td><td><span data-option="windows">windows, </span><span data-option="blackhole">blackhole, </span><span data-option="network">network</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-blackhole-chaos">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 CPU hog</strong></td><td>Windows EC2 CPU hog stresses configurable CPU cores on Windows EC2 instances.</td><td><span data-option="cpu">cpu, </span><span data-option="stress">stress, </span><span data-option="windows">windows</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-cpu-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 memory hog</strong></td><td>Windows EC2 memory hog consumes memory inside Windows EC2 instances.</td><td><span data-option="memory">memory, </span><span data-option="stress">stress, </span><span data-option="windows">windows</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-memory-hog">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 network latency</strong></td><td>Windows EC2 network latency adds latency to traffic destined for target IPs or hosts.</td><td><span data-option="network">network, </span><span data-option="latency">latency, </span><span data-option="windows">windows</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-network-latency">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 network loss</strong></td><td>Windows EC2 network loss drops a configurable percentage of packets to target IPs or hosts.</td><td><span data-option="network">network, </span><span data-option="loss">loss, </span><span data-option="windows">windows</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-network-loss">Chaos faults for AWS</a></td></tr><tr><td><strong>Windows EC2 process kill</strong></td><td>Windows EC2 process kill kills processes selected by PID or process name on Windows EC2 instances.</td><td><span data-option="process">process, </span><span data-option="kill">kill, </span><span data-option="windows">windows, </span><span data-option="ec2">ec2</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/aws/aws.md#windows-ec2-process-kill">Chaos faults for AWS</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FoiunvGhhmegPHTJQu5WD%2Fimage.png?alt=media&amp;token=eb6c7bf6-87eb-474f-ac88-8b5e95e4aecc" alt="" data-size="line"> <strong>Fault templates for Azure</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="4-W2A35A" label="AKS" color="blue"></option><option value="TNd_hrV7" label="node down" color="blue"></option><option value="DQPfnGpm" label="kubernetes" color="blue"></option><option value="dME0hILx" label="disk loss" color="blue"></option><option value="-2gJwGXI" label="CPU hog" color="blue"></option><option value="I1flmg-X" label="I/O stress" color="blue"></option><option value="nA5LHLkO" label="memory hog" color="blue"></option><option value="kvKOYosH" label="azure" color="blue"></option><option value="25I6rz7l" label="service bus" color="blue"></option><option value="V9_Y2ta0" label="messaging" color="blue"></option><option value="oYm6tt5A" label="restrict access" color="blue"></option><option value="1pq6LldR" label="stop" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Azure AKS node down</strong></td><td>Deallocate a percentage of AKS worker VMs (selected by node pool and zone) for a configurable duration, then start them again.</td><td><span data-option="4-W2A35A">AKS, </span><span data-option="TNd_hrV7">node down, </span><span data-option="DQPfnGpm">kubernetes</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-aks-node-down">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure disk loss</strong></td><td>Detach one or more managed data disks from their attached VMs for a configurable duration, then reattach them on the same LUN.</td><td><span data-option="dME0hILx">disk loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-disk-loss">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure instance CPU hog</strong></td><td>Drive CPU utilization to a configurable target on one or more Azure VMs for a configurable duration via the VM run-command extension.</td><td><span data-option="-2gJwGXI">CPU hog</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-instance-cpu-hog">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure instance IO stress</strong></td><td>Drive sustained disk read/write IO on one or more Azure VMs for a configurable duration via the VM run-command extension.</td><td><span data-option="I1flmg-X">I/O stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-instance-io-stress">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure instance memory hog</strong></td><td>Consume a configurable amount of memory on one or more Azure VMs for a configurable duration via the VM run-command extension.</td><td><span data-option="nA5LHLkO">memory hog</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-instance-memory-hog">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure instance stop</strong></td><td>Stop one or more Azure VMs (or VMSS instances) for a configurable duration, then start them again.</td><td><span data-option="kvKOYosH">azure</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-instance-stop">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure Service Bus queue state change</strong></td><td>Change the operational status of one or more Service Bus queues (Disabled, SendDisabled, ReceiveDisabled) for a configurable duration, then restore Active.</td><td><span data-option="25I6rz7l">service bus, </span><span data-option="V9_Y2ta0">messaging</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-service-bus-queue-state-change">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure web app access restrict</strong></td><td>Add an Access Restriction rule to one or more App Service web apps for a configurable duration so callers in the blocked range receive 403 Forbidden.</td><td><span data-option="oYm6tt5A">restrict access</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-web-app-access-restrict">Chaos faults for Azure</a></td></tr><tr><td><strong>Azure web app stop</strong></td><td>Stop one or more App Service web apps for a configurable duration, then start them again.</td><td><span data-option="1pq6LldR">stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/azure/azure.md#azure-web-app-stop">Chaos faults for Azure</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2Fbbb0ixczCnWJYfDbivGp%2Fimage.png?alt=media&amp;token=8292ca9f-ad1a-4e76-953f-321d28c444cc" alt="" data-size="line"><strong>Fault templates for Cloud Foundry</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="K57vkuIV" label="cf" color="blue"></option><option value="_qD_iCWA" label="cloud-foundry" color="blue"></option><option value="7Q90XgMl" label="app" color="blue"></option><option value="cR7YJrt_" label="stop" color="blue"></option><option value="laqKm74Z" label="container" color="blue"></option><option value="6poOhV64" label="kill" color="blue"></option><option value="bSXTTzpC" label="route" color="blue"></option><option value="q2cogDls" label="jvm" color="blue"></option><option value="bV9kdy-w" label="cpu" color="blue"></option><option value="Pyr3luSq" label="memory" color="blue"></option><option value="ZeVM_qzC" label="gc" color="blue"></option><option value="hRxvCmAT" label="exception" color="blue"></option><option value="i3-n0DLj" label="latency" color="blue"></option><option value="xeamKSn5" label="return" color="blue"></option><option value="oO2L35SH" label="network" color="blue"></option><option value="z5RBBnS6" label="loss" color="blue"></option><option value="3N29RSr_" label="corruption" color="blue"></option><option value="AYjfGjH6" label="duplication" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CF app stop</strong></td><td>Stop a Cloud Foundry app for a configurable duration and then re-start it, so you can test how the platform and consumers react when the app goes offline.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="cR7YJrt_">stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-stop">Cloud Foundry</a></td></tr><tr><td><strong>CF app container kill</strong></td><td>Kill the container of one or more app instances and let Cloud Foundry reschedule them so you can validate platform self-healing and peer absorption.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="laqKm74Z">container, </span><span data-option="6poOhV64">kill</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-container-kill">Cloud Foundry</a></td></tr><tr><td><strong>CF app route unmap</strong></td><td>Temporarily unmap a route from a Cloud Foundry app so you can test how upstream gateways and consumers handle a route that returns 404 from the CF router.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="bSXTTzpC">route</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-route-unmap">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM CPU stress</strong></td><td>Drive sustained CPU usage inside the JVM of a Java app instance for a configurable duration so you can test the app under CPU saturation.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="bV9kdy-w">cpu</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-cpu-stress">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM memory stress</strong></td><td>Drive heap or non-heap memory pressure inside the JVM of a Java app instance so you can test GC behavior and out-of-memory handling.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="Pyr3luSq">memory</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-memory-stress">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM trigger GC</strong></td><td>Force a full garbage-collection cycle inside the JVM of a Java app instance so you can measure pause time and tail-latency impact.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="ZeVM_qzC">gc</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-trigger-gc">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM method exception</strong></td><td>Force a specific JVM method to throw a configurable exception so you can validate error-handling paths in callers.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="hRxvCmAT">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-method-exception">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM method latency</strong></td><td>Add artificial latency to every invocation of a specific JVM method so you can simulate a slow downstream call at the method boundary.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="i3-n0DLj">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-method-latency">Cloud Foundry</a></td></tr><tr><td><strong>CF app JVM modify return</strong></td><td>Override the return value of a specific JVM method so you can test defensive checks and fallbacks against unexpected values.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="q2cogDls">jvm, </span><span data-option="xeamKSn5">return</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-jvm-modify-return">Cloud Foundry</a></td></tr><tr><td><strong>CF app network latency</strong></td><td>Add latency on the egress traffic of an app instance so you can simulate a slow downstream dependency at the network layer.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="oO2L35SH">network, </span><span data-option="i3-n0DLj">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-network-latency">Cloud Foundry</a></td></tr><tr><td><strong>CF app network loss</strong></td><td>Drop a configurable percentage of egress packets from an app instance so you can test retransmissions, retries, and circuit-breaker behavior.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="oO2L35SH">network, </span><span data-option="z5RBBnS6">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-network-loss">Cloud Foundry</a></td></tr><tr><td><strong>CF app network corruption</strong></td><td>Corrupt a configurable percentage of egress packets from an app instance so you can validate TCP retransmissions and protocol parsers.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="oO2L35SH">network, </span><span data-option="3N29RSr_">corruption</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-network-corruption">Cloud Foundry</a></td></tr><tr><td><strong>CF app network duplication</strong></td><td>Duplicate a configurable percentage of egress packets from an app instance so you can validate idempotency and deduplication logic.</td><td><span data-option="K57vkuIV">cf, </span><span data-option="_qD_iCWA">cloud-foundry, </span><span data-option="7Q90XgMl">app, </span><span data-option="oO2L35SH">network, </span><span data-option="AYjfGjH6">duplication</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/cloud-foundry/cloud-foundry.md#cf-app-network-duplication">Cloud Foundry</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2Fj1FkIkDppMIOOtkq9XSF%2Fimage.png?alt=media&amp;token=cdf0866d-490c-4afd-b689-85c19f7a8e58" alt="" data-size="line"> <strong>Fault templates for GCP</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="7IBWOwfu" label="instance" color="blue"></option><option value="srab6dlv" label="failover" color="blue"></option><option value="uu0pX2n_" label="disk loss" color="blue"></option><option value="UD1FtqSM" label="instance stop" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GCP SQL instance failover</strong></td><td>Trigger a failover on a high-availability Cloud SQL instance so you can test how the application behaves when the primary node fails over to its standby.</td><td><span data-option="7IBWOwfu">instance, </span><span data-option="srab6dlv">failover</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md#gcp-sql-instance-failover">Chaos faults for GCP</a></td></tr><tr><td><strong>GCP VM disk loss by label</strong></td><td>Detach a percentage of non-boot persistent disks selected by label from GCP VM instances for a configurable duration, then reattach them.</td><td><span data-option="uu0pX2n_">disk loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md#gcp-vm-disk-loss-by-label">Chaos faults for GCP</a></td></tr><tr><td><strong>GCP VM disk loss</strong></td><td>Detach one or more named non-boot persistent disks from GCP VM instances for a configurable duration, then reattach them.</td><td><span data-option="uu0pX2n_">disk loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md#gcp-vm-disk-loss">Chaos faults for GCP</a></td></tr><tr><td><strong>GCP VM instance stop by label</strong></td><td>Stop a percentage of Compute Engine VMs selected by label for a configurable duration, then start them again (or rely on the MIG auto-healer).</td><td><span data-option="UD1FtqSM">instance stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md#gcp-vm-instance-stop-by-label">Chaos faults for GCP</a></td></tr><tr><td><strong>GCP VM instance stop</strong></td><td>Stop one or more named Compute Engine VMs for a configurable duration, then start them again (or rely on the MIG auto-healer).</td><td><span data-option="UD1FtqSM">instance stop</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/gcp/gcp.md#gcp-vm-instance-stop">Chaos faults for GCP</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FWUAZdSpaQpnK8Xnl2GSD%2Fimage.png?alt=media&amp;token=982eb0e1-f310-417e-beac-498a46dbb0ba" alt="" data-size="line"> <strong>Fault templates for Kube-Resilience</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="79H1G6Ikjukf" label="kubelet" color="blue"></option><option value="yufGY3wStx4r" label="density" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Kubelet density</strong></td><td>Create a configurable number of pods on a target Kubernetes node so you can test how the node, kubelet, and workload behave during a sudden pod-storm.</td><td><span data-option="79H1G6Ikjukf">kubelet, </span><span data-option="yufGY3wStx4r">density</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kube-resilience/kubelet-density.md">Kubelet Density</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FXVNLR1xlGRSQtNLyYWT7%2Fimage.png?alt=media&amp;token=448a377d-f311-4fc1-907b-d42fef543614" alt="" data-size="line"> <strong>Fault templates for Kubernetes</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="1cikGlXW" label="node" color="blue"></option><option value="i4yGY7Od" label="pod" color="blue"></option><option value="FHocnRsR" label="jvm" color="blue"></option><option value="c1iPgDfX" label="exception" color="blue"></option><option value="3G0SdEWG" label="cpu" color="blue"></option><option value="lQRCI8O7" label="memory" color="blue"></option><option value="FRoXe7KT" label="solace" color="blue"></option><option value="pFhCT9-6" label="latency" color="blue"></option><option value="nuj7tpFO" label="sql" color="blue"></option><option value="mw7jaMXO" label="mongo" color="blue"></option><option value="pkCBN78p" label="kafka" color="blue"></option><option value="-LDdnruv" label="redis" color="blue"></option><option value="ts7BiJbk" label="cache" color="blue"></option><option value="wDlA-H_T" label="expire" color="blue"></option><option value="kZpcZN9A" label="function" color="blue"></option><option value="Nf0A87Di" label="error" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Kubelet service kill</strong></td><td>Kubelet service kill makes the application unreachable on the account of the node turning unschedulable (NotReady).</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#kubelet-service-kill">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node CPU hog</strong></td><td>Node CPU hog exhausts the CPU resources on a Kubernetes node.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-cpu-hog">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node drain</strong></td><td>Node drain drains the node of all its resources running on it.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-drain">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node IO stress</strong></td><td>Node IO stress causes I/O stress on the Kubernetes node.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-io-stress">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node memory hog</strong></td><td>Node memory hog causes memory resource exhaustion on the Kubernetes node.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-memory-hog">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node network latency</strong></td><td>Node network latency introduces network latency to the Kubernetes node.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-network-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node network loss</strong></td><td>Node network loss introduces packet loss in the Kubernetes node.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-network-loss">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node restart</strong></td><td>Node restart disrupts the state of the node by restarting it.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-restart">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Node taint</strong></td><td>Node taint taints (contaminates) the node by applying the desired effect.</td><td><span data-option="1cikGlXW">node</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#node-taint">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Container kill</strong></td><td>Container kill terminates a single container inside a target pod, leaving the pod scheduled so the container restarts in place.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#container-kill">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Disk fill</strong></td><td>Disk fill consumes a configurable percentage of a target container's ephemeral storage to test eviction and write-failure handling.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#disk-fill">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>FS fill</strong></td><td>FS fill writes a configurable amount of data into a specific path inside a target container to test mounted-volume capacity and write-failure handling.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#fs-fill">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API block</strong></td><td>Pod API block drops selected API requests or responses on a target pod using path, method, header, query, and source or destination filters (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-block">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API latency</strong></td><td>Pod API latency adds a configurable delay to selected API calls on a target pod with path, method, header, query, and source or destination filters (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API modify body</strong></td><td>Pod API modify body overwrites request or response bodies on selected API calls of a target pod using path, method, header, query, and source or destination filters (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-modify-body">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API modify header</strong></td><td>Pod API modify header overrides request or response headers on selected API calls of a target pod using path, method, query, and source or destination filters (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-modify-header">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API status code</strong></td><td>Pod API status code overrides the HTTP status code returned by selected API calls of a target pod using path, method, header, query, and source or destination filters (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-status-code">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod API modify response custom</strong></td><td>Pod API modify response custom combines status code, header, and body modifications on selected API calls of a target pod in a single experiment (with HTTPS support).</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-api-modify-response-custom">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod autoscaler</strong></td><td>Pod autoscaler scales a target Deployment or StatefulSet to a configured replica count for a fixed duration to test cluster capacity and node autoscaling.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-autoscaler">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod CPU hog</strong></td><td>Pod CPU hog consumes excess CPU resources of the application container.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-cpu-hog">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod delete</strong></td><td>Pod delete removes one or more pods of a target workload to test replica availability, controller recovery, and graceful termination.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-delete">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod DNS error</strong></td><td>Pod DNS error fails DNS lookups from inside a target pod for selected hostnames (or all hostnames) to test how the application handles upstream lookup failures.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-dns-error">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod DNS spoof</strong></td><td>Pod DNS spoof redirects DNS lookups for selected hostnames inside a target pod to a different address so the application opens connections to the wrong destination.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-dns-spoof">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod HTTP latency</strong></td><td>Pod HTTP latency adds a configurable delay to HTTP responses served by a target pod on a chosen service port to test client timeouts, retries, and tail-latency budgets.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-http-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod HTTP modify body</strong></td><td>Pod HTTP modify body overwrites the HTTP response body served by a target pod to test client behavior under corrupted, empty, or unexpected payloads.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-http-modify-body">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod HTTP modify header</strong></td><td>Pod HTTP modify header overrides HTTP request or response headers on a target pod to test resilience to missing, altered, or unexpected header values.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-http-modify-header">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod HTTP reset peer</strong></td><td>Pod HTTP reset peer forcibly resets TCP connections carrying HTTP requests to a target pod after a configurable delay to test client retry, connection-pool, and circuit-breaker behavior.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-http-reset-peer">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod HTTP status code</strong></td><td>Pod HTTP status code overrides the HTTP response status code returned by a target pod (and optionally overwrites the body) to test client error handling on specific HTTP statuses.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-http-status-code">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod IO attribute override</strong></td><td>Pod IO attribute override rewrites file attributes returned by stat syscalls on a target container's mounted volume to test how the application reacts to changed permissions, ownership, size, or timestamps.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-io-attribute-override">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod IO error</strong></td><td>Pod IO error makes filesystem syscalls on a target container's mounted volume return a configurable error code so you can validate how the application handles failed reads, writes, and opens.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-io-error">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod IO latency</strong></td><td>Pod IO latency adds a configurable delay to filesystem syscalls against a target container's mounted volume so you can test how the application behaves under slow storage.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-io-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod IO mistake</strong></td><td>Pod IO mistake seeds wrong bytes into reads or writes against a target container's mounted volume so you can validate how the application detects and recovers from silent data corruption.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-io-mistake">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod IO stress</strong></td><td>Pod IO stress generates sustained filesystem read and write load inside a target container's mounted volume to test disk pressure, slow IO, and ephemeral-storage exhaustion.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-io-stress">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM method exception</strong></td><td>Pod JVM method exception causes a specific Java method in a target JVM to throw a configurable exception on every invocation so you can test how callers handle the failure.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-method-exception">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM CPU stress</strong></td><td>Pod JVM CPU stress drives a configurable number of CPU cores inside a target JVM to test how the application behaves when its Java process is starved of CPU.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="3G0SdEWG">cpu</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-cpu-stress">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM memory stress</strong></td><td>Pod JVM memory stress injects JVM memory stress for a Java process executing in a Kubernetes pod by consuming excessive memory resources of the JVM.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="lQRCI8O7">memory</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-memory-stress">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM modify return</strong></td><td>Pod JVM modify return overrides the return value of a specific Java method in a target JVM so you can test how callers behave when a method silently returns wrong data.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-modify-return">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Solace Latency</strong></td><td>Pod JVM Solace Latency adds a configurable delay to Solace publisher or subscriber calls from a target JVM, scoped by topic or queue, to test timeout and back-pressure behavior under slow Solace messaging.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="FRoXe7KT">solace, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-solace-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Solace Exception</strong></td><td>Pod JVM Solace Exception causes Solace publisher or subscriber calls from a target JVM to throw a configurable exception on a chosen topic or queue so you can test caller error handling.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="FRoXe7KT">solace, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-solace-exception">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM method latency</strong></td><td>Pod JVM method latency adds a configurable delay to every invocation of a specific Java method in a target JVM so you can test how callers and dependents behave under slow methods.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-method-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM trigger gc</strong></td><td>Pod JVM trigger gc forces an immediate full garbage collection in a target JVM so you can measure GC pause impact on latency, throughput, and downstream timeouts.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-trigger-gc">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM SQL Exception</strong></td><td>Pod JVM SQL Exception causes JDBC calls from a target JVM to throw a configurable exception, scoped by table and SQL operation, so you can test how the application handles database failures.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="nuj7tpFO">sql, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-sql-exception">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM SQL Latency</strong></td><td>Pod JVM SQL Latency adds a configurable delay to JDBC calls from a target JVM, scoped by table and SQL operation, so you can test connection-pool exhaustion and timeout handling under slow databases.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="nuj7tpFO">sql, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-sql-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Mongo Exception</strong></td><td>Pod JVM Mongo Exception causes MongoDB calls from a target JVM to throw a configurable exception, scoped by database and collection, so you can test how the application handles MongoDB failures.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="mw7jaMXO">mongo, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-mongo-exception">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Mongo Latency</strong></td><td>Pod JVM Mongo Latency adds a configurable delay to MongoDB calls from a target JVM, scoped by database and collection, so you can test how the application behaves under slow MongoDB operations.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="mw7jaMXO">mongo, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-mongo-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Kafka Exception</strong></td><td>Pod JVM Kafka Exception causes Kafka producer or consumer calls from a target JVM to throw a configurable exception on a chosen topic so you can test how the application handles Kafka failures.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="pkCBN78p">kafka, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-kafka-exception">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod JVM Kafka Latency</strong></td><td>Pod JVM Kafka Latency adds a configurable delay to Kafka producer or consumer calls from a target JVM on a chosen topic so you can test how the application behaves under slow Kafka messaging.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="FHocnRsR">jvm, </span><span data-option="pkCBN78p">kafka, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-jvm-kafka-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod memory hog</strong></td><td>Pod memory hog consumes memory resources in excess, resulting in a significant spike in the memory usage of a pod.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-memory-hog">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network corruption</strong></td><td>Pod network corruption flips random bits in a configurable percentage of packets on a target container's network path.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-corruption">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network duplication</strong></td><td>Pod network duplication injects chaos to disrupt the network connectivity to Kubernetes pods.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-duplication">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network latency</strong></td><td>Pod network latency adds a configurable delay to packets on a target container's network path.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network loss</strong></td><td>Pod network loss drops a configurable percentage of packets on a target container's network path.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-loss">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network partition</strong></td><td>Pod network partition blocks 100% ingress and egress traffic of the target application by creating network policy.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-partition">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod network rate limit</strong></td><td>Pod network rate limit fault generates Traffic Control (tc) rules with Token Bucket Filter (TBF) to assess Kubernetes pod resilience under limited network bandwidth condition.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-network-rate-limit">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Redis cache penetration</strong></td><td>Redis cache penetration issues a configurable burst of reads for keys that do not exist against a target Redis instance to test downstream database load and null-cache protection.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="-LDdnruv">redis, </span><span data-option="ts7BiJbk">cache</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#redis-cache-penetration">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Redis cache expire</strong></td><td>Redis cache expire expires a configurable set of keys (or all keys) on a target Redis instance to test cold-cache resilience, refill behavior, and downstream database back-pressure.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="-LDdnruv">redis, </span><span data-option="wDlA-H_T">expire</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#redis-cache-expire">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Redis cache limit</strong></td><td>Redis cache limit caps the maximum memory of a target Redis instance to force evictions and out-of-memory write errors, then restores the original limit when the fault ends.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="ts7BiJbk">cache, </span><span data-option="-LDdnruv">redis</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#redis-cache-limit">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Time chaos</strong></td><td>Time chaos shifts the wall-clock or monotonic time observed by selected processes inside a target container to test application behavior under clock skew, token expiry, and time-based scheduling errors.</td><td><span data-option="i4yGY7Od">pod</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#time-chaos">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod Application Function Error</strong></td><td>Pod Application Function Error makes a specific instrumented application function return a configurable error on a chosen percentage of invocations so you can test caller error handling and recovery.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="kZpcZN9A">function, </span><span data-option="Nf0A87Di">error</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-application-function-error">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod Application Function Latency</strong></td><td>Pod Application Function Latency adds a configurable delay to invocations of a specific instrumented application function so you can test how callers and dependents behave under slow functions.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="kZpcZN9A">function, </span><span data-option="pFhCT9-6">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-application-function-latency">Chaos Faults for Kubernetes</a></td></tr><tr><td><strong>Pod Application Function Exception</strong></td><td>Pod Application Function Exception throws a configurable exception from a specific instrumented application function so you can test how callers and dependents handle thrown failures, including retry filters and circuit breakers.</td><td><span data-option="i4yGY7Od">pod, </span><span data-option="kZpcZN9A">function, </span><span data-option="c1iPgDfX">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/kubernetes/kubernetes.md#pod-application-function-exception">Chaos Faults for Kubernetes</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FDFmfcpQ0swriNRdgTPrB%2Fimage.png?alt=media&amp;token=73d45b1f-95de-4e12-8ca8-51e2662c05f8" alt="" data-size="line"> <strong>Fault templates for Linux</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="Lx1aK9pQ" label="linux" color="blue"></option><option value="Cq7mV2sR" label="cpu" color="blue"></option><option value="St4nY8wH" label="stress" color="blue"></option><option value="Me6rT3uD" label="memory" color="blue"></option><option value="Di9kP5xB" label="disk" color="blue"></option><option value="Io2fN7cL" label="io" color="blue"></option><option value="Fs8jQ4vM" label="fs" color="blue"></option><option value="Dn3sH6zA" label="dns" color="blue"></option><option value="Ne5tR1kC" label="network" color="blue"></option><option value="Lo7sW9bE" label="loss" color="blue"></option><option value="La4tX2mG" label="latency" color="blue"></option><option value="Co6rU8pJ" label="corruption" color="blue"></option><option value="Du1pL3qF" label="duplication" color="blue"></option><option value="Ra9eI5nK" label="rate-limit" color="blue"></option><option value="Pr2oC7dS" label="process" color="blue"></option><option value="Se8vB4hT" label="service" color="blue"></option><option value="Ti3mZ6rV" label="time" color="blue"></option><option value="Jv5mQ1xN" label="jvm" color="blue"></option><option value="Mt7hK9pW" label="method" color="blue"></option><option value="Ex4cR2uY" label="exception" color="blue"></option><option value="Mo6dL8aP" label="modify" color="blue"></option><option value="Re1tF3nD" label="return" color="blue"></option><option value="Tr9gV5sH" label="trigger" color="blue"></option><option value="Gc2pX7mK" label="gc" color="blue"></option><option value="Ap8iN4qB" label="api" color="blue"></option><option value="Bl3oC6rM" label="block" color="blue"></option><option value="Bo7dT1vE" label="body" color="blue"></option><option value="He5aU9kL" label="header" color="blue"></option><option value="Sc4oP2xJ" label="status-code" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Linux CPU stress</strong></td><td>Linux CPU stress runs WORKERS busy workers at LOAD percent utilization each on the target Linux machine for DURATION. Use it to test how a workload behaves when compute headroom shrinks.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Cq7mV2sR">cpu, </span><span data-option="St4nY8wH">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-cpu-stress">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux memory stress</strong></td><td>Linux memory stress allocates MEMORY of memory across WORKERS workers on the target Linux machine for DURATION. Use it to test how a workload behaves under memory pressure and OOM conditions.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Me6rT3uD">memory, </span><span data-option="St4nY8wH">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-memory-stress">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux disk fill</strong></td><td>Linux disk fill writes a file under FILL_PATH until it occupies FILL_STORAGE for DURATION, then removes the file. Use it to test how a workload behaves when its writable storage fills up.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Di9kP5xB">disk</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-disk-fill">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux disk IO stress</strong></td><td>Linux disk I/O stress runs WORKERS I/O workers that consume FILE_SYSTEM_UTILISATION of the filesystem at VOLUME_MOUNT_PATH for DURATION. Use it to test how a workload behaves when disk bandwidth is saturated.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Di9kP5xB">disk, </span><span data-option="Io2fN7cL">io, </span><span data-option="St4nY8wH">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-disk-io-stress">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux fs fill</strong></td><td>Linux fs fill writes a file under FILL_PATH until it occupies FILL_STORAGE for DURATION, then removes the file. Use it to test how a workload behaves when its writable storage fills up.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Fs8jQ4vM">fs, </span><span data-option="Di9kP5xB">disk</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-fs-fill">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux DNS error</strong></td><td>Linux DNS error returns DNS failures for host names matching HOST_NAMES on the target Linux machine for DURATION. Use it to test how a workload behaves during a DNS outage.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Dn3sH6zA">dns</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-dns-error">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux DNS spoof</strong></td><td>Linux DNS spoof resolves host names in SPOOF_MAP to the configured spoofed IPs on the target Linux machine for DURATION. Use it to test how a workload behaves when DNS resolves to unexpected endpoints.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Dn3sH6zA">dns</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-dns-spoof">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux network loss</strong></td><td>Linux network loss drops NETWORK_PACKET_LOSS_PERCENTAGE percent of packets leaving the target Linux machine on NETWORK_INTERFACES for DURATION. Use it to test how a workload behaves when the network is unreliable.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ne5tR1kC">network, </span><span data-option="Lo7sW9bE">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-network-loss">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux network latency</strong></td><td>Linux network latency adds NETWORK_LATENCY milliseconds of delay to packets leaving the target Linux machine on NETWORK_INTERFACES for DURATION. Use it to test how a workload behaves when the network is slow.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ne5tR1kC">network, </span><span data-option="La4tX2mG">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-network-latency">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux network corruption</strong></td><td>Linux network corruption bit-flips NETWORK_PACKET_CORRUPTION_PERCENTAGE percent of egress packets on the target Linux machine for DURATION. Use it to test how a workload behaves when packet payloads are damaged.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ne5tR1kC">network, </span><span data-option="Co6rU8pJ">corruption</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-network-corruption">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux network duplication</strong></td><td>Linux network duplication duplicates NETWORK_PACKET_DUPLICATION_PERCENTAGE percent of egress packets on the target Linux machine for DURATION. Use it to test how a workload behaves under at-least-once delivery.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ne5tR1kC">network, </span><span data-option="Du1pL3qF">duplication</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-network-duplication">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux network rate limit</strong></td><td>Linux network rate limit throttles egress bandwidth on the target Linux machine to NETWORK_BANDWIDTH (with BURST and LIMIT) for DURATION. Use it to test how a workload behaves when bandwidth is constrained.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ne5tR1kC">network, </span><span data-option="Ra9eI5nK">rate-limit</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-network-rate-limit">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux process kill</strong></td><td>Linux process kill terminates processes matching PROCESS_IDS, PROCESS_NAMES, or PROCESS_COMMAND on the target Linux machine for DURATION. Use it to test how a workload behaves when a critical process disappears.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Pr2oC7dS">process</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-process-kill">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux service restart</strong></td><td>Linux service restart stops the systemd services in SERVICES and starts them again after INTERVAL, repeating for DURATION. Use it to test how a workload behaves when a critical service flaps.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Se8vB4hT">service</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-service-restart">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux time chaos</strong></td><td>Linux time chaos skews the system clock on the target Linux machine by OFFSET for DURATION. Use it to test how a workload behaves when time jumps forward or backward.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ti3mZ6rV">time</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-time-chaos">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM CPU stress</strong></td><td>Linux JVM CPU stress uses Byteman to pin CPU cores of busy work inside the target Java process for DURATION. Use it to test how a Java workload behaves when its own threads pin the CPU.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Cq7mV2sR">cpu, </span><span data-option="St4nY8wH">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-cpu-stress">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM memory stress</strong></td><td>Linux JVM memory stress uses Byteman to consume memory in the heap or stack of the target Java process for DURATION. Use it to test how a Java workload behaves under memory pressure.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Me6rT3uD">memory, </span><span data-option="St4nY8wH">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-memory-stress">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM method exception</strong></td><td>Linux JVM method exception uses Byteman to throw EXCEPTION from CLASS.METHOD of the target Java process for DURATION. Use it to test how a Java workload handles unexpected exceptions.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Mt7hK9pW">method, </span><span data-option="Ex4cR2uY">exception</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-method-exception">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM method latency</strong></td><td>Linux JVM method latency uses Byteman to add LATENCY milliseconds of delay to every invocation of CLASS.METHOD in the target Java process for DURATION. Use it to test how a Java workload behaves when an internal method slows down.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Mt7hK9pW">method, </span><span data-option="La4tX2mG">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-method-latency">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM modify return</strong></td><td>Linux JVM modify return uses Byteman to overwrite the return value of CLASS.METHOD with RETURN in the target Java process for DURATION. Use it to test how callers handle unexpected return data.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Mo6dL8aP">modify, </span><span data-option="Re1tF3nD">return</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-modify-return">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux JVM trigger GC</strong></td><td>Linux JVM trigger GC uses Byteman to force garbage collection events in the target Java process for DURATION. Use it to test how a Java workload behaves under repeated GC pressure.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Jv5mQ1xN">jvm, </span><span data-option="Tr9gV5sH">trigger, </span><span data-option="Gc2pX7mK">gc</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-jvm-trigger-gc">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux API block</strong></td><td>Linux API block starts a local proxy on the target Linux machine and returns STATUS_CODE for matching API calls for DURATION. Use it to test how callers handle a sudden API outage.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ap8iN4qB">api, </span><span data-option="Bl3oC6rM">block</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-api-block">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux API latency</strong></td><td>Linux API latency starts a local proxy on the target Linux machine and adds LATENCY of delay to matching API requests for DURATION. Use it to test how callers handle slow API responses.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ap8iN4qB">api, </span><span data-option="La4tX2mG">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-api-latency">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux API modify body</strong></td><td>Linux API modify body starts a local proxy on the target Linux machine and overwrites the body of matching API calls with RESPONSE_BODY for DURATION. Use it to test how callers handle unexpected payloads.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ap8iN4qB">api, </span><span data-option="Mo6dL8aP">modify, </span><span data-option="Bo7dT1vE">body</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-api-modify-body">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux API modify header</strong></td><td>Linux API modify header starts a local proxy on the target Linux machine and replaces header values in matching API calls with the keys/values from HEADERS_MAP for DURATION. Use it to test how callers handle altered headers.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ap8iN4qB">api, </span><span data-option="He5aU9kL">header, </span><span data-option="Mo6dL8aP">modify</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-api-modify-header">Chaos Faults for Linux</a></td></tr><tr><td><strong>Linux API status code</strong></td><td>Linux API status code starts a local proxy on the target Linux machine and overrides matching API responses with STATUS_CODE (and optionally RESPONSE_BODY) for DURATION. Use it to test how callers handle specific error responses.</td><td><span data-option="Lx1aK9pQ">linux, </span><span data-option="Ap8iN4qB">api, </span><span data-option="Sc4oP2xJ">status-code</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/linux/linux.md#linux-api-status-code">Chaos Faults for Linux</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FZgQpgfqrxKZRHJZj79Vs%2Fimage.png?alt=media&amp;token=df2a44f8-8843-4925-a6de-5320f8e0f63c" alt="" data-size="line"> <strong>Fault templates for Load</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="srab6dlv" label="failover" color="blue"></option><option value="uu0pX2n_" label="disk loss" color="blue"></option><option value="b14aaqekshiu" label="load" color="blue"></option><option value="Hkun7NYsD3Gs" label="k6" color="blue"></option><option value="7neIctXPI6yq" label="loadgen" color="blue"></option><option value="6yiVTsnBKGxA" label="locust" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>k6 loadgen</strong></td><td>Run a Grafana k6 script against a target HTTP endpoint for a configurable duration so you can test how the workload behaves under scripted load.</td><td><span data-option="b14aaqekshiu">load, </span><span data-option="Hkun7NYsD3Gs">k6, </span><span data-option="7neIctXPI6yq">loadgen</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/load/k6-loadgen.md">K6 Loadgen</a></td></tr><tr><td><strong>Locust loadgen</strong></td><td>Run a Locust script against a target HTTP endpoint for a configurable duration so you can test how the workload behaves under Python-defined load.</td><td><span data-option="b14aaqekshiu">load, </span><span data-option="6yiVTsnBKGxA">locust, </span><span data-option="7neIctXPI6yq">loadgen</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/load/locust-loadgen.md">Locust Loadgen</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2F88UJRNTRUhEUTdeu9Nas%2Fimage.png?alt=media&amp;token=4f667747-f821-457c-a444-2ffdff591b61" alt="" data-size="line"> <strong>Fault templates for SSH</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select><option value="LZJh3biJ4fL1" label="ssh" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>SSH chaos</strong></td><td>Run a user-supplied inject script on a remote host over SSH for a configurable duration, with a rollback script invoked on completion or abort.</td><td><span data-option="LZJh3biJ4fL1">ssh</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/ssh/ssh-chaos.md">SSH Chaos</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FGxVahvDlxW7cRoNFmRI1%2Fimage.png?alt=media&amp;token=9f3f66a0-940d-41ca-9d8e-d8359059307f" alt="" data-size="line"> <strong>Fault templates for VMware</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="cpu" label="CPU" color="blue"></option><option value="stress" label="stress" color="blue"></option><option value="memory" label="memory" color="blue"></option><option value="io" label="io" color="blue"></option><option value="network" label="network" color="blue"></option><option value="latency" label="latency" color="blue"></option><option value="loss" label="loss" color="blue"></option><option value="rate" label="rate" color="blue"></option><option value="limit" label="limit" color="blue"></option><option value="dns" label="DNS" color="blue"></option><option value="http" label="http" color="blue"></option><option value="reset" label="reset" color="blue"></option><option value="peer" label="peer" color="blue"></option><option value="modify" label="modify" color="blue"></option><option value="response" label="response" color="blue"></option><option value="kill" label="kill" color="blue"></option><option value="process" label="process" color="blue"></option><option value="stop" label="stop" color="blue"></option><option value="service" label="service" color="blue"></option><option value="power" label="power" color="blue"></option><option value="off" label="off" color="blue"></option><option value="moid" label="moid" color="blue"></option><option value="name" label="name" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>VMware CPU hog</strong></td><td>Drive CPU utilization to a configurable percentage across a configurable number of cores on a Linux VMware VM for a configurable duration.</td><td><span data-option="cpu">CPU, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-cpu-hog">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware memory hog</strong></td><td>Consume a configurable amount of RAM on a Linux VMware VM for a configurable duration so you can test how the workload behaves when memory headroom shrinks.</td><td><span data-option="memory">memory, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-memory-hog">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware IO stress</strong></td><td>Drive disk IO load on a Linux VMware VM for a configurable duration so you can test how the workload behaves when storage throughput is saturated.</td><td><span data-option="io">io, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-io-stress">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware network latency</strong></td><td>Add latency to egress traffic from a Linux VMware VM for a configurable duration. Scope by destination IP, hostname, or port.</td><td><span data-option="network">network, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-network-latency">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware network loss</strong></td><td>Drop a configurable percentage of egress packets from a Linux VMware VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="loss">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-network-loss">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware network rate limit</strong></td><td>Cap egress bandwidth on a Linux VMware VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="rate">rate, </span><span data-option="limit">limit</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-network-rate-limit">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware DNS chaos</strong></td><td>Force DNS resolution failures for specific hostnames on a Linux VMware VM for a configurable duration.</td><td><span data-option="dns">DNS, </span><span data-option="stress">stress</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-dns-chaos">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware HTTP latency</strong></td><td>Inject HTTP response latency at a target service running inside a Linux VMware VM for a configurable duration.</td><td><span data-option="http">http, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-http-latency">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware HTTP reset peer</strong></td><td>Reset TCP connections to an HTTP service running inside a Linux VMware VM for a configurable duration.</td><td><span data-option="http">http, </span><span data-option="reset">reset, </span><span data-option="peer">peer</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-http-reset-peer">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware HTTP response modify</strong></td><td>Rewrite HTTP responses (status code, body, headers) from a service running inside a Linux VMware VM for a configurable duration.</td><td><span data-option="http">http, </span><span data-option="modify">modify, </span><span data-option="response">response</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-http-response-modify">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware process kill</strong></td><td>Terminate one or more processes by PID inside a Linux VMware VM for a configurable duration.</td><td><span data-option="kill">kill, </span><span data-option="process">process</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-process-kill">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware service stop</strong></td><td>Stop one or more systemd services inside a Linux VMware VM for a configurable duration.</td><td><span data-option="stop">stop, </span><span data-option="service">service</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-service-stop">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware VM poweroff</strong></td><td>Power off one or more VMware VMs (identified by Managed Object ID) for a configurable duration, then power them back on.</td><td><span data-option="power">power, </span><span data-option="off">off, </span><span data-option="moid">moid</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-vm-poweroff">Chaos faults for VMware</a></td></tr><tr><td><strong>VMware VM poweroff by name</strong></td><td>Power off one or more VMware VMs (identified by name) for a configurable duration, then power them back on.</td><td><span data-option="power">power, </span><span data-option="off">off, </span><span data-option="name">name</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/vmware/vmware.md#vmware-vm-poweroff-by-name">Chaos faults for VMware</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2F8QXcKvYVDCfHu0uWr8zT%2Fimage.png?alt=media&amp;token=7679ba52-2637-4aa8-b10a-cd677498f0ee" alt="" data-size="line"> <strong>Fault templates for Windows</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="cpu" label="cpu" color="blue"></option><option value="memory" label="memory" color="blue"></option><option value="disk" label="disk" color="blue"></option><option value="process" label="process" color="blue"></option><option value="kill" label="kill" color="blue"></option><option value="network" label="network" color="blue"></option><option value="blackhole" label="blackhole" color="blue"></option><option value="latency" label="latency" color="blue"></option><option value="loss" label="loss" color="blue"></option><option value="corruption" label="corruption" color="blue"></option><option value="duplication" label="duplication" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Windows CPU stress</strong></td><td>Drive CPU utilization to a configurable percentage across a configurable number of cores on a Windows VM for a configurable duration.</td><td><span data-option="cpu">cpu</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-cpu-stress">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows memory stress</strong></td><td>Consume a configurable amount of memory on a Windows VM for a configurable duration so you can test how the workload behaves when memory headroom shrinks.</td><td><span data-option="memory">memory</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-memory-stress">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows disk stress</strong></td><td>Drive disk IO load on a Windows VM for a configurable duration so you can test how the workload behaves when storage throughput is saturated.</td><td><span data-option="disk">disk</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-disk-stress">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows process kill</strong></td><td>Terminate one or more processes (by PID or name) on a Windows VM for a configurable duration.</td><td><span data-option="process">process, </span><span data-option="kill">kill</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-process-kill">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows blackhole chaos</strong></td><td>Block all network traffic to selected destination hosts or IP addresses from a Windows VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="blackhole">blackhole</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-blackhole-chaos">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows network latency</strong></td><td>Add latency to egress traffic from a Windows VM for a configurable duration. Scope by destination IP, hostname, port, or protocol.</td><td><span data-option="network">network, </span><span data-option="latency">latency</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-network-latency">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows network loss</strong></td><td>Drop a configurable percentage of egress packets from a Windows VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="loss">loss</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-network-loss">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows network corruption</strong></td><td>Corrupt a configurable percentage of egress packets from a Windows VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="corruption">corruption</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-network-corruption">Chaos faults for Windows</a></td></tr><tr><td><strong>Windows network duplication</strong></td><td>Duplicate a configurable percentage of egress packets from a Windows VM for a configurable duration.</td><td><span data-option="network">network, </span><span data-option="duplication">duplication</span></td><td><a href="/resilience-testing/chaos-engineering/faults/chaos-fault-categories/windows/windows.md#windows-network-duplication">Chaos faults for Windows</a></td></tr></tbody></table>

</details>
{% endtab %}

{% tab title="Probe Templates" %}
Built-in probe templates grouped by platform. Select a platform to browse its probe templates.

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FvhciVGZWx0ywyJq6nXiG%2Fimage.png?alt=media&amp;token=11fb3fc6-e3a0-4345-a450-78347bee5fae" alt="" data-size="line"> <strong>Probe templates for AWS</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="ec2" label="ec2" color="blue"></option><option value="instance" label="instance" color="blue"></option><option value="status" label="status" color="blue"></option><option value="health-check" label="health-check" color="blue"></option><option value="ecs" label="ecs" color="blue"></option><option value="service" label="service" color="blue"></option><option value="scaling" label="scaling" color="blue"></option><option value="lambda" label="lambda" color="blue"></option><option value="function" label="function" color="blue"></option><option value="serverless" label="serverless" color="blue"></option><option value="load-balancer" label="load-balancer" color="blue"></option><option value="alb" label="alb" color="blue"></option><option value="clb" label="clb" color="blue"></option><option value="availability-zone" label="availability-zone" color="blue"></option><option value="security-group" label="security-group" color="blue"></option><option value="rules" label="rules" color="blue"></option><option value="network" label="network" color="blue"></option><option value="access-control" label="access-control" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>AWS EC2 Instance Status Check</strong></td><td>Validates the current state of an EC2 instance. This probe checks if the specified EC2 instance(s) are in the expected state.</td><td><span data-option="ec2">ec2, </span><span data-option="instance">instance, </span><span data-option="status">status, </span><span data-option="health-check">health-check</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/aws/index.md#aws-ec2-instance-status-check">AWS</a></td></tr><tr><td><strong>AWS ECS Service Status Check</strong></td><td>Validates the status of an Amazon ECS service. This probe checks if the specified ECS service has reached the desired state.</td><td><span data-option="ecs">ecs, </span><span data-option="service">service, </span><span data-option="status">status, </span><span data-option="scaling">scaling</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/aws/index.md#aws-ecs-service-status-check">AWS</a></td></tr><tr><td><strong>AWS Lambda Function Status Check</strong></td><td>This probe checks if a Lambda function exists and is in the 'Active' state.</td><td><span data-option="lambda">lambda, </span><span data-option="function">function, </span><span data-option="status">status, </span><span data-option="serverless">serverless</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/aws/index.md#aws-lambda-function-status-check">AWS</a></td></tr><tr><td><strong>AWS Load Balancer AZ Check</strong></td><td>Validates the availability of target availability zone(s) in the given ALB or CLB.</td><td><span data-option="load-balancer">load-balancer, </span><span data-option="alb">alb, </span><span data-option="clb">clb, </span><span data-option="availability-zone">availability-zone</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/aws/index.md#aws-load-balancer-az-check">AWS</a></td></tr><tr><td><strong>AWS Security Group Rule Check</strong></td><td>Validates the presence of rules in AWS security groups.</td><td><span data-option="security-group">security-group, </span><span data-option="rules">rules, </span><span data-option="network">network, </span><span data-option="access-control">access-control</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/aws/index.md#aws-security-group-rule-check">AWS</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2Fj1FkIkDppMIOOtkq9XSF%2Fimage.png?alt=media&amp;token=cdf0866d-490c-4afd-b689-85c19f7a8e58" alt="" data-size="line"> <strong>Probe templates for GCP</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="sql" label="sql" color="blue"></option><option value="database" label="database" color="blue"></option><option value="cloud-sql" label="cloud-sql" color="blue"></option><option value="status-check" label="status-check" color="blue"></option><option value="disk" label="disk" color="blue"></option><option value="storage" label="storage" color="blue"></option><option value="persistent-disk" label="persistent-disk" color="blue"></option><option value="compute-engine" label="compute-engine" color="blue"></option><option value="vm" label="vm" color="blue"></option><option value="instance" label="instance" color="blue"></option><option value="virtual-machine" label="virtual-machine" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GCP SQL Instance Status Check</strong></td><td>Validates if a GCP Cloud SQL instance is in Running state.</td><td><span data-option="sql">sql, </span><span data-option="database">database, </span><span data-option="cloud-sql">cloud-sql, </span><span data-option="status-check">status-check</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/gcp/index.md#gcp-sql-instance-status-check">GCP</a></td></tr><tr><td><strong>GCP VM Disk Status Check</strong></td><td>Validates if a GCP Compute Engine persistent disk is in ready to use state.</td><td><span data-option="disk">disk, </span><span data-option="storage">storage, </span><span data-option="persistent-disk">persistent-disk, </span><span data-option="compute-engine">compute-engine</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/gcp/index.md#gcp-vm-disk-status-check">GCP</a></td></tr><tr><td><strong>GCP VM Instance Status Check</strong></td><td>Validates if a GCP Compute Engine VM instance is in Running state.</td><td><span data-option="vm">vm, </span><span data-option="instance">instance, </span><span data-option="compute-engine">compute-engine, </span><span data-option="virtual-machine">virtual-machine</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/gcp/index.md#gcp-vm-instance-status-check">GCP</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FXVNLR1xlGRSQtNLyYWT7%2Fimage.png?alt=media&amp;token=448a377d-f311-4fc1-907b-d42fef543614" alt="" data-size="line"> <strong>Probe templates for Kubernetes</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="container" label="container" color="blue"></option><option value="restart" label="restart" color="blue"></option><option value="pod" label="pod" color="blue"></option><option value="health-check" label="health-check" color="blue"></option><option value="node" label="node" color="blue"></option><option value="status" label="status" color="blue"></option><option value="cluster" label="cluster" color="blue"></option><option value="replica" label="replica" color="blue"></option><option value="deployment" label="deployment" color="blue"></option><option value="availability" label="availability" color="blue"></option><option value="resource" label="resource" color="blue"></option><option value="cpu" label="cpu" color="blue"></option><option value="memory" label="memory" color="blue"></option><option value="startup" label="startup" color="blue"></option><option value="performance" label="performance" color="blue"></option><option value="timing" label="timing" color="blue"></option><option value="health" label="health" color="blue"></option><option value="running" label="running" color="blue"></option><option value="warnings" label="warnings" color="blue"></option><option value="events" label="events" color="blue"></option><option value="monitoring" label="monitoring" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Container Restart Check</strong></td><td>Container restart check validates the restart count of a container.</td><td><span data-option="container">container, </span><span data-option="restart">restart, </span><span data-option="pod">pod, </span><span data-option="health-check">health-check</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#container-restart-check">Kubernetes</a></td></tr><tr><td><strong>Node Status Check</strong></td><td>Node status check validates the current state of Kubernetes nodes.</td><td><span data-option="node">node, </span><span data-option="status">status, </span><span data-option="cluster">cluster, </span><span data-option="health-check">health-check</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#node-status-check">Kubernetes</a></td></tr><tr><td><strong>Pod Replica Count Check</strong></td><td>Pod replica count check validates the current replica count of Kubernetes pods.</td><td><span data-option="pod">pod, </span><span data-option="replica">replica, </span><span data-option="deployment">deployment, </span><span data-option="availability">availability</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#pod-replica-count-check">Kubernetes</a></td></tr><tr><td><strong>Pod Resource Utilisation Check</strong></td><td>Pod resource utilisation check validates the current resource utilisation metrics of Kubernetes pods.</td><td><span data-option="pod">pod, </span><span data-option="resource">resource, </span><span data-option="cpu">cpu, </span><span data-option="memory">memory</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#pod-resource-utilisation-check">Kubernetes</a></td></tr><tr><td><strong>Pod Startup Time Check</strong></td><td>Pod startup time check validates the startup time of Kubernetes pods.</td><td><span data-option="pod">pod, </span><span data-option="startup">startup, </span><span data-option="performance">performance, </span><span data-option="timing">timing</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#pod-startup-time-check">Kubernetes</a></td></tr><tr><td><strong>Pod Status Check</strong></td><td>Pod status check validates the current state of Kubernetes pods.</td><td><span data-option="pod">pod, </span><span data-option="status">status, </span><span data-option="health">health, </span><span data-option="running">running</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#pod-status-check">Kubernetes</a></td></tr><tr><td><strong>Pod Warnings Check</strong></td><td>Pod warnings check checks for warnings in the pod events.</td><td><span data-option="pod">pod, </span><span data-option="warnings">warnings, </span><span data-option="events">events, </span><span data-option="monitoring">monitoring</span></td><td><a href="/resilience-testing/chaos-engineering/use-chaos-engineering/probes/probe-templates/kubernetes/index.md#pod-warnings-check">Kubernetes</a></td></tr></tbody></table>

</details>

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FWUAZdSpaQpnK8Xnl2GSD%2Fimage.png?alt=media&amp;token=982eb0e1-f310-417e-beac-498a46dbb0ba" alt="" data-size="line"> <strong>Probe templates for Datadog</strong></summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="datadog" label="datadog" color="blue"></option><option value="cpu" label="cpu" color="blue"></option><option value="metrics" label="metrics" color="blue"></option><option value="kubernetes" label="kubernetes" color="blue"></option><option value="memory" label="memory" color="blue"></option><option value="apm" label="apm" color="blue"></option><option value="latency" label="latency" color="blue"></option><option value="p95" label="p95" color="blue"></option><option value="p99" label="p99" color="blue"></option><option value="avg" label="avg" color="blue"></option><option value="error-rate" label="error-rate" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Datadog CPU Check</strong></td><td>Validates the CPU utilisation of a service using Datadog container metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="cpu">cpu, </span><span data-option="metrics">metrics, </span><span data-option="kubernetes">kubernetes</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-cpu-check.md">Datadog CPU Check</a></td></tr><tr><td><strong>Datadog Memory Check</strong></td><td>Validates the memory utilisation of a service using Datadog container metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="memory">memory, </span><span data-option="metrics">metrics, </span><span data-option="kubernetes">kubernetes</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-memory-check.md">Datadog Memory Check</a></td></tr><tr><td><strong>Datadog P95 Latency Check</strong></td><td>Validates the p95 latency of a service using Datadog APM metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="apm">apm, </span><span data-option="latency">latency, </span><span data-option="p95">p95</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-p95-latency-check.md">Datadog P95 Latency Check</a></td></tr><tr><td><strong>Datadog P99 Latency Check</strong></td><td>Validates the p99 latency of a service using Datadog APM metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="apm">apm, </span><span data-option="latency">latency, </span><span data-option="p99">p99</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-p99-latency-check.md">Datadog P99 Latency Check</a></td></tr><tr><td><strong>Datadog Avg Latency Check</strong></td><td>Validates the average latency of a service using Datadog APM metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="apm">apm, </span><span data-option="latency">latency, </span><span data-option="avg">avg</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-avg-latency-check.md">Datadog Avg Latency Check</a></td></tr><tr><td><strong>Datadog Error Rate Check</strong></td><td>Validates the error rate of a service using Datadog APM metrics.</td><td><span data-option="datadog">datadog, </span><span data-option="apm">apm, </span><span data-option="error-rate">error-rate</span></td><td><a href="/resilience-testing/chaos-testing/probes/probe-template-library/datadog/datadog-error-rate-check.md">Datadog Error Rate Check</a></td></tr></tbody></table>

</details>
{% endtab %}

{% tab title="Action Templates" %}
Built-in action templates grouped by type. Select a type to browse its action templates.

<details>

<summary><img src="https://3217710372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmV5EkLS9r45VPaoUnJZ%2Fuploads%2FXVNLR1xlGRSQtNLyYWT7%2Fimage.png?alt=media&amp;token=448a377d-f311-4fc1-907b-d42fef543614" alt="" data-size="line"> Action templates for custom script executions</summary>

<table data-view="cards"><thead><tr><th></th><th></th><th><select multiple><option value="zvAVPXSTgvVC" label="grafana" color="blue"></option><option value="mS1aDBFimk8c" label="observability" color="blue"></option><option value="HCAkBq0WaM9F" label="annotation" color="blue"></option><option value="GmVxoNWgnpxs" label="datadog" color="blue"></option><option value="bMT6T6fJh92g" label="event" color="blue"></option></select></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Grafana Chaos Annotation</strong></td><td>Grafana chaos annotation action annotates the grafana dashboard to highlight the chaos duration.</td><td><span data-option="zvAVPXSTgvVC">grafana, </span><span data-option="mS1aDBFimk8c">observability, </span><span data-option="HCAkBq0WaM9F">annotation</span></td><td><a href="/resilience-testing/chaos-testing/action-templates/custom-script/grafana-chaos-annotation.md">Grafana Chaos Annotation</a></td></tr><tr><td><strong>Datadog Chaos Event</strong></td><td>It creates an event for the datadog dashboard to highlight the chaos injection.</td><td><span data-option="GmVxoNWgnpxs">datadog, </span><span data-option="mS1aDBFimk8c">observability, </span><span data-option="bMT6T6fJh92g">event</span></td><td><a href="/resilience-testing/chaos-testing/action-templates/custom-script/datadog-chaos-event.md">Datadog Chaos Event</a></td></tr></tbody></table>

</details>
{% endtab %}
{% endtabs %}

{% @harness-feedback/feedback %}
