Netflix/chaosmonkey

Chaos Monkey is a resiliency tool that helps applications tolerate random instance failures.

Owned by Netflix

View on GitHub ↗Jump to charts ↓

Netflix/chaosmonkey has 17k+ stars and 1k+ forks on GitHub, is written in Go, and was last pushed on Jan 6, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Added to GitGenius on October 12th, 2026
Created on October 18th, 2016
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 1,305
Total Stargazers: 17,178 (+0)
Total Subscribers: 660 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 days
Mean response time: 42.6 days
90th percentile: 266.2 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,239 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • help wanted (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Chaos Monkey is a resiliency tool that randomly terminates virtual machine instances and containers running in production environments to help applications tolerate failures.

The tool addresses the problem of services that lack resilience by deliberately injecting failure into production systems. By randomly killing instances, it exposes engineers to real-world failure scenarios during normal operations, encouraging them to design systems that can withstand such disruptions. This approach follows the Principles of Chaos Engineering and makes failure a regular part of the development and operational workflow rather than an unexpected crisis.

Chaos Monkey is suited for teams already using Spinnaker for continuous delivery, as the tool is fully integrated with that platform and requires it for operation. It works with any backend that Spinnaker supports, including AWS, Google Compute Engine, Azure, Kubernetes, and Cloud Foundry, though it has been tested specifically with AWS, GCE, and Kubernetes. Organizations should adopt this tool if they want to systematically validate their application resilience and build a culture where engineers proactively design for failure rather than assuming infrastructure stability.

The project maintains active engagement with its user community through a dedicated support group. Development activity shows consistent attention to the tool's core functionality and its integration with the broader Spinnaker ecosystem. The codebase is written in Go, reflecting a focus on building a lightweight, efficient binary suitable for production deployment.