14 docs tagged with "cloud-foundry-faults"

Kill the container of a Cloud Foundry app instance so you can test how the platform reschedules it and how peers absorb traffic during the gap.

Drive CPU saturation inside the JVM of a Cloud Foundry app instance so you can test how the application and the platform react to sustained CPU pressure.

Drive heap or non-heap memory pressure inside the JVM of a Cloud Foundry app instance so you can test how the application reacts to sustained memory exhaustion.

Make a specific JVM method throw an exception inside a Cloud Foundry app instance so you can test how callers handle synchronous failures.

Add artificial latency to a specific JVM method inside a Cloud Foundry app instance so you can test how slow downstream calls cascade through the system.

Override the return value of a specific JVM method inside a Cloud Foundry app instance so you can test caller behavior against unexpected return values.

Trigger a full garbage collection cycle inside the JVM of a Cloud Foundry app instance so you can measure pause time and tail-latency impact.

Corrupt a configurable percentage of egress packets from a Cloud Foundry app instance so you can test how TCP retransmissions and protocol handlers cope.

Duplicate a configurable percentage of egress packets from a Cloud Foundry app instance so you can test deduplication logic and idempotency assumptions.

Inject network latency on the egress of a Cloud Foundry app instance so you can test how the app and its callers behave when downstream calls become slow.

Drop a configurable percentage of egress packets from a Cloud Foundry app instance so you can test retry, timeout, and circuit-breaker behavior.

Temporarily unmap a route from a Cloud Foundry app so you can test how upstream consumers behave when the app becomes unreachable via that route.

Stop a Cloud Foundry app for a configurable duration, then restart it, so you can test how the platform and dependents react when the app goes offline.

Catalog of Cloud Foundry chaos faults that disrupt apps, JVM runtimes, and the network between app instances and their dependencies.