Chaos Engineering & Resilience

Safe, hypothesis-driven failure experiments, from a first pod kill in staging to game days, failover drills and continuous chaos in production, with findings tracked until the fix is proven.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Chaos Engineering & Resilience, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Chaos Engineering & Resilience

Deliberately injecting failures in controlled experiments to prove systems degrade gracefully and recover without human heroics.

  1. Resilience risk inventory for one critical service
  2. Steady-state metrics for the first experiment
  3. Chaos experiment safety charter and stop rules
  4. Experiment hypothesis and record format
  5. Choosing a fault injection tool
  6. Dependency failure mode map
  7. Staging environment fit for chaos experiments
  8. First pod termination experiment in staging
  9. Stakeholder briefing before the first experiment
  10. Monthly game day rhythm
  11. Chaos experiment backlog grooming
  12. Weekly experiment run slot
  13. Resilience findings follow-through
  14. Chaos experiments in the delivery pipeline
  15. Quarterly disaster recovery failover drill
  16. Backup restore verification routine
  17. Chaos results log and monthly digest
  18. Annual resilience posture review
  19. Resilience patterns study, timeouts, retries and breakers
  20. Chaos engineering reading list and case studies
  21. Network fault injection practice
  22. Writing falsifiable chaos hypotheses
  23. Blast radius and progressive scope expansion
  24. Facilitating a game day as game master
  25. Live experiment observation and timeline
  26. Fault flags inside application code
  27. Timeout and retry budget audit
  28. Circuit breaker on the riskiest dependency
  29. Graceful degradation plan for non-critical features
  30. Retry storm and thundering herd experiment
  31. Single availability zone loss experiment
  32. Database primary failover experiment
  33. DNS, certificate and secret expiry experiments
  34. Disk, memory and connection exhaustion experiments
  35. Deciding when chaos moves to production
  36. First cross-team game day
  37. Region evacuation exercise before peak season
  38. Third-party outage tabletop exercise
  39. Pre-launch resilience readiness review
  40. Shared platform dependency blackout day
  41. Chaos engineering for a small team without SRE
  42. Enterprise chaos programme charter
  43. Operational resilience evidence for regulated firms
  44. Resilience testing on a serverless stack
  45. Introducing chaos to a sceptical organisation
  46. Chaos experiments on a legacy monolith
  47. Continuous chaos in production with automatic abort
  48. Clock skew and time-dependent failure experiments
  49. Metastable failure and overload recovery analysis
  50. Network partition testing with consistency checks

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Resilience risk inventory for one critical service

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Chaos experiments chosen at random find random things, while experiments chosen from a list of known risks find the outages you were going to have anyway.

First tasks

  • Pick the one service whose outage would cost the business most
  • Pull the last year of incident reports that touched this service
  • List failure scenarios by layer and score likelihood and impact
  • Mark the top five scenarios as first experiment candidates

Steady-state metrics for the first experiment

An experiment can only prove something if you know what normal looks like before you break anything. Choosing two or three business-level signals, such as orders per minute or successful sign-ins, plus their usual range by hour of day, gives every later experiment a clear pass or fail line. Without this, teams argue afterwards about whether a wobble on a dashboard mattered.

First tasks

  • Ask the product owner which number they would check first during an outage
  • Export a week of that signal and note its range by hour
  • Build one dashboard showing every steady-state signal together
  • Write the failure threshold for each signal on the dashboard itself

Chaos experiment safety charter and stop rules

Nothing ends a chaos programme faster than an experiment that causes a real outage nobody approved. A one-page charter stating who may run experiments, where, at what times, how they are announced and exactly when they are halted protects customers and the programme's reputation together. Write it before the first experiment, not after the first scare.

First tasks

  • Draft the allowed environments, hours and excluded dates on one page
  • Write stop rules that reference the steady-state thresholds
  • Test the halt mechanism for each fault type you plan to inject
  • Get sign-off from the service owner and the on-call lead

Make it yours.

Install Chaos Engineering & Resilience, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.