A chaos engineering library for Elixir inspired by Netflix's Chaos Monkey. Mutineer allows you to inject controlled, random failures into your functions to test resilience and error handling.
- Wrap functions to randomly trigger failures at configurable rates
- Multiple failure types: errors, exceptions, timeouts, nil returns, and process exits
- Minimal runtime overhead when disabled
- Two flexible APIs: attribute-based decorators or explicit macros
- Disabled by default for safety
Add mutineer to your list of dependencies in mix.exs:
defdepsdo[{:mutineer,"~> 0.2.0"}]endConfigure Mutineer in your config/config.exs (or environment-specific config):
config:mutineer,Mutineer,enabled: true,default_failure_rate: 0.1,default_failure_types: :errorAdd the use Mutineer statement to your module.
You can then use the @chaos attribute to mark functions for chaos injection:
defmoduleMyApp.DatabasedouseMutineer@chaosfailure_rate: 0.2defquery(sql)do# Your database query logicend@chaosfailure_type: :timeout,delay: 3000defslow_query(sql)do# This will randomly timeoutendendUse defchaos or defchaosp (for private functions) for explicit chaos wrapping:
defmoduleMyApp.ExternalServicedouseMutineerdefchaoscall_api(endpoint),failure_rate: 0.3,failure_type: :raisedo# Your API call logicenddefchaospinternal_helper(data),failure_rate: 0.1do# Private function with chaosendendenabled- Enables or disables chaos globally (default:false)default_failure_types- Sets the default failure types for all functions, can be a list of failure types or a single failure type (default::error)default_failure_rate- Sets the default failure rate for all functions (default:0.1)
:error- Returns{:error, :mutineer_chaos}(default) or a random error from theerrorsoption:raise- Raises either aMutineer.ChaosErrorexception (default) or a custom error specified in theraised_errorsoption:delay- Introduces a random delay (1-5 seconds) before executing function:timeout- Same as:raise, but with a random delay before raising the exception:nil- Returnsnil:exit- Callsexit(:mutineer_chaos); the atom can be specified in theexit_errorsoption
Options can be passed to @chaos, defchaos, or defchaosp:
failure_rateis the probability of failure for a given function (0.0-1.0), where1.0or above will always failfailure_types(orfailure_type) is either a list of failure types to trigger (e.g.[:error, :delay]) or a single failure type (e.g.:error)errors(orerror) is either a list of objects to be randomly selected from or a single object to return when the:errortype is triggeredraised_errors(orraised_error) is a list of errors to be randomly selected from or a single error to be raised when the:raisetype is triggeredexit_errors(orexit_error) is a list of errors to be randomly selected from or a single error to be raised when the:exittype is triggereddelayis the upperbound of the delay in milliseconds or a range of milliseconds for:timeoutand:delaytypes
defmoduleMyApp.PaymentGatewaydouseMutineer@chaosfailure_rate: 0.1,failure_type: :errordefprocess_payment(amount,card)do# Payment processing logic{:ok,%{transaction_id: "txn_123",amount: amount}}end@chaosfailure_rate: 0.05,failure_type: :raise,message: "Gateway timeout"defverify_card(card)do# Card verification logic{:ok,:valid}endend# In your tests or staging environment:caseMyApp.PaymentGateway.process_payment(100,card)do{:ok,result}->handle_success(result){:error,reason}->handle_error(reason)end# config/dev.exsconfig:mutineer,Mutineer,enabled: true,default_failure_rate: 0.1# config/prod.exsconfig:mutineer,Mutineer,enabled: false