VMware CPU hog
Consume CPU resources on a Linux VMware VM for a configurable duration so you can test how the workload behaves when compute headroom shrinks.
Consume CPU resources on a Linux VMware VM for a configurable duration so you can test how the workload behaves when compute headroom shrinks.
Force DNS resolution failures for specific hostnames inside a Linux VMware VM so you can test how the workload behaves when DNS is unhealthy.
Inject HTTP response latency on a target service running inside a Linux VMware VM so you can test how callers behave when a downstream service slows down.
Reset TCP connections to an HTTP service running inside a Linux VMware VM so you can test how callers behave when the service rudely drops connections.
Rewrite HTTP responses (status code, body, headers) from a service running inside a Linux VMware VM so you can test how callers behave when responses are corrupted.
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.
Consume a configurable amount of memory on a Linux VMware VM for a configurable duration so you can test how the workload behaves when memory headroom shrinks.
Inject network latency on egress traffic from a Linux VMware VM for a configurable duration so you can test how the workload behaves under slow networks.
Drop a configurable percentage of egress packets on a Linux VMware VM so you can test how the workload behaves when packet loss spikes.
Cap egress bandwidth on a Linux VMware VM so you can test how the workload behaves when network throughput is throttled.
Kill one or more processes inside a Linux VMware VM for a configurable duration so you can test how supervisors and application logic recover.
Stop one or more services inside a Linux VMware VM for a configurable duration so you can test how the workload behaves when a managed service is down.
Power off one or more VMware VMs (identified by Managed Object ID) for a configurable duration so you can test how applications behave when a VM disappears.
Power off one or more VMware VMs (identified by name) for a configurable duration so you can test how applications behave when a VM disappears.