| Linux CPU stress | 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. | linux, cpu, stress | #linux-cpu-stress |
| Linux memory stress | 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. | linux, memory, stress | #linux-memory-stress |
| Linux disk fill | 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. | linux, disk | #linux-disk-fill |
| Linux disk IO stress | 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. | linux, disk, io, stress | #linux-disk-io-stress |
| Linux fs fill | 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. | linux, fs, disk | #linux-fs-fill |
| Linux DNS error | 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. | linux, dns | #linux-dns-error |
| Linux DNS spoof | 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. | linux, dns | #linux-dns-spoof |
| Linux network loss | 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. | linux, network, loss | #linux-network-loss |
| Linux network latency | 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. | linux, network, latency | #linux-network-latency |
| Linux network corruption | 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. | linux, network, corruption | #linux-network-corruption |
| Linux network duplication | 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. | linux, network, duplication | #linux-network-duplication |
| Linux network rate limit | 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. | linux, network, rate-limit | #linux-network-rate-limit |
| Linux process kill | 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. | linux, process | #linux-process-kill |
| Linux service restart | 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. | linux, service | #linux-service-restart |
| Linux time chaos | 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. | linux, time | #linux-time-chaos |
| Linux JVM CPU stress | 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. | linux, jvm, cpu, stress | #linux-jvm-cpu-stress |
| Linux JVM memory stress | 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. | linux, jvm, memory, stress | #linux-jvm-memory-stress |
| Linux JVM method exception | 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. | linux, jvm, method, exception | #linux-jvm-method-exception |
| Linux JVM method latency | 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. | linux, jvm, method, latency | #linux-jvm-method-latency |
| Linux JVM modify return | 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. | linux, jvm, modify, return | #linux-jvm-modify-return |
| Linux JVM trigger GC | 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. | linux, jvm, trigger, gc | #linux-jvm-trigger-gc |
| Linux API block | 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. | linux, api, block | #linux-api-block |
| Linux API latency | 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. | linux, api, latency | #linux-api-latency |
| Linux API modify body | 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. | linux, api, modify, body | #linux-api-modify-body |
| Linux API modify header | 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. | linux, api, header, modify | #linux-api-modify-header |
| Linux API status code | 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. | linux, api, status-code | #linux-api-status-code |