~/talk

The Psychology of Chaos Engineering

Talkat DevOpsDays Raleigh 2019 · 2019-10-01..10-02· [devops-and-delivery]
slides:none on file

Chaos engineering proves to be structured experimentation that increases system resilience while risking human stress if mishandled; case studies show technical wins with negative team impact unless culture, communication, and observability are addressed. Examples include Chaos Monkey/Simian Army, Gremlin, Chaos Toolkit, PagerDuty’s internal chaos cat and Optum’s chaos slinger; techniques stress minimizing blast radius (start with canary 1%), measure simple signals like stream starts per minute, define stop conditions, and run workshops and tabletop exercises before production.

AI-written summary · about

  1. 0:00Introduction
  2. 3:10What is chaos engineering
  3. 3:50What is chaos engineering about
  4. 7:00Observability
  5. 7:55Minimize Blast Radius
  6. 9:20Tools
  7. 12:05Bruce Wong
  8. 13:40Management
  9. 15:20Get people to participate
  10. 16:40Know your conditions
  11. 17:30Dont cause stress on your people
  12. 18:20Be transparent
  13. 19:20Open source tools
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.