11 docs tagged with "api-chaos"

Block API requests passing through a target Linux machine for a configurable duration by returning a configured status code, so you can test how callers handle a sudden API outage.

Add latency to API requests passing through a target Linux machine for a configurable duration so you can test how callers handle slow API responses.

Replace API request or response bodies passing through a target Linux machine for a configurable duration so you can test how callers handle unexpected payloads.

Override HTTP headers on API requests or responses passing through a target Linux machine for a configurable duration so you can test how callers handle altered headers.

Override the HTTP status code (and optionally the response body) of API responses passing through a target Linux machine for a configurable duration.

Block selected API requests or responses on a target Kubernetes pod using path, method, header, query parameter, and source or destination filters to test client retry and failover behavior.

Add a configurable delay to selected API calls on a target Kubernetes pod using path, method, header, query, and source or destination filters to test client timeouts, retries, and tail-latency budgets.

Overwrite API request or response bodies on a target Kubernetes pod using path, method, header, query, and source or destination filters to test client behavior under corrupted payloads.

Override API request or response headers on a target Kubernetes pod using path, method, query, and source or destination filters to test resilience to missing, altered, or unexpected header values.

Combine status code, header, and body modifications on selected API calls of a target Kubernetes pod in a single fault, with filtering by path, method, query, source, or destination.

Override the HTTP status code returned by selected API calls on a target Kubernetes pod using path, method, header, query, and source or destination filters to test client error handling and circuit-breaker behavior.