Chaos Monkey for Spring Boot
codecentric.github.io
- Free plan
- API
- Self-hosted
What Chaos Monkey for Spring Boot is
Chaos Monkey for Spring Boot is a free, open-source, self-hosted tool for examining how running Spring Boot applications behave under disruption. It can add latency, throw configured exceptions, terminate applications, and apply CPU or memory pressure. Watchers can target annotated Spring beans, health indicators, RestTemplate and WebClient beans, Actuator components, outgoing requests, or configured beans by name or class. The project can be added as a dependency or loaded externally when a Spring Boot application starts. With Spring Boot Actuator included, HTTP and JMX endpoints can change configuration at runtime. Documentation describes Unleash feature-toggle control and springdoc-openapi display in Swagger UI. Micrometer-backed metrics can connect with systems including Datadog, Prometheus, New Relic, Graphite, and Influx. Network fault injection, experiment scheduling, and blast-radius controls are listed; cloud fault injection is not. Each version targets a specific Spring Boot version, creating a compatibility constraint.
Who it suits
It suits teams testing resilience and operational behavior in Spring Boot applications. It is aimed at self-hosted environments where engineers can control dependencies, experiments, and monitoring.
Good to know, and what to watch
- Free and open source
- Supports latency and exception attacks
- Targets selected beans and requests
- Runtime control through Actuator endpoints
- Integrates with monitoring systems
- No cloud fault injection
- Versions target specific Spring Boot releases
- Wrong external JAR version may break applications
- Experiments require operational caution
The verdict
Chaos Monkey for Spring Boot provides configurable disruptions and runtime controls for Spring Boot resilience work. Teams should match each release to their Spring Boot version and follow the project’s guidance to begin with noncritical services outside production.
What the maker publishes
- Activation
- You can add it as a project dependency or load it as an external dependency when starting a Spring Boot application. source
- Attack types
- Documented assaults include latency, exceptions, application termination, memory, and CPU load. source
- Compatibility limit
- Each Chaos Monkey version is built for a specific Spring Boot version, and using the external JAR with a different Spring Boot version may break the application. source
- Compatibility limit
- Each Chaos Monkey release is built for a specific Spring Boot version, and using the external JAR with a different version may break the application. source
- Configuration
- Configuration can be changed at runtime through Spring Boot Actuator HTTP or JMX endpoints; Actuator must be included in the project dependencies for this feature. source
- Feature flags
- The project supports feature toggles and includes minimal configuration for using Unleash to control them. source
- Founded
- 2004 source
- Headquarters
- Solingen, Germany source
- Integration
- Add it as a project dependency or load it as an external dependency when starting a Spring Boot app. source
- Integrations
- The documentation describes using Unleash to control feature toggles and springdoc-openapi to show Chaos Monkey endpoints in Swagger UI. source
- Intended users
- The project is for teams testing the resilience and operational behavior of Spring Boot applications. source
- Intended users
- The project is focused on Spring Boot applications and aims to help test application behavior such as fallbacks, network latency, and service failures. source
- Monitoring integrations
- Through Spring Boot’s Micrometer-backed metrics facade, the guide lists monitoring systems including Datadog, Prometheus, New Relic, Graphite, and Influx. source
- Open source
- The project is open source and welcomes contributions. source
- Open source
- The project is open source and welcomes contributions. source
- Operational guidance
- The project recommends checking service resilience and monitoring, defining steady states, and starting experiments on a noncritical service outside production. source
- Purpose
- Chaos Monkey for Spring Boot attacks running Spring Boot applications to help test how they behave during operation. source
- Purpose
- Chaos Monkey for Spring Boot tests Spring Boot applications by injecting failures during operation. source
- Request attacks
- Request assaults can add latency or throw configured runtime exceptions when watched methods are called. source
- Runtime attacks
- Runtime assaults can target the application’s CPU, memory, or availability through the AppKiller assault. source
- Runtime controls
- Spring Boot Actuator HTTP and JMX endpoints can expose controls for changing configuration at runtime. source
- Security and compliance
- The repository identifies its license as Apache-2.0; the project pages opened do not state a product security certification or compliance claim. source
- Security guidance
- The project advises checking resilience and monitoring, defining steady states, starting with a noncritical service, and gaining experience outside production before running experiments in production. source
- Support
- The project directs bug reports and feature requests to GitHub issues and general usage questions to Stack Overflow with the spring-boot-chaos-monkey tag. source
Checked against the maker's pages on 8 Oct 2026.