Chaos engineering delivers evidence of system weakness; system verification helps chaos engineering bring context and business value so that you can make better decisions about where to focus your resources to improve a system's reliability. This talk was given by Russ Miles, CEO of ChaosIQ, at the London Chaos and Resilience Engineering meetup on 28/01/2020

1. From Chaos to Verification
Bringing the “Why!?” to Chaos Engineering

2. A confession…

4. “Chaos Engineering’s sole purpose
is to provide evidence
of system weaknesses”

5. Challenge 1?

6. The term…

7. Challenge 2?

8. Questions…

9. What experiments should I run?

10. What next??
or …
What does it mean??

11. And from the business…

12. “What should I take a risk on
exploring?”

13. Even more crucially…

14. “How do I decide
what to invest in?”

15. Chaos Engineering is valuable,
but can be risky and expensive…

16. Planning & Running Game Days…

17. Creating automated
chaos experiments…

18. Processing results into
communicable evidence

19. “How do I decide
what to invest in?”
IS HARD

20. Current tooling sucks at this…

21. Low Level “Conditions”

22. Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence

23. Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence

24. Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards

25. High Level “Decisions”
Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards

26. High Level “Decisions”
Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards
Analysis? Learning? Action?

27. High Level “Decisions”
Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards
Analysis? Learning? Action?

28. High Level “Decisions”
Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards
Analysis? Learning? Action?

29. From Chaos to Verification

30. Chaos Engineering

31. Chaos Engineering
Hypothesis?

32. Chaos Engineering
Hypothesis?
Experiment

33. Chaos Engineering
Hypothesis?
Experiment
Deviation?

34. Chaos Engineering
Hypothesis?
Evidence
Experiment
Deviation?

35. Chaos Engineering
Hypothesis?
Evidence
Experiment
Steady-State
Deviation?

36. Chaos Engineering
Hypothesis?
Evidence
Experiment
Steady-State Method
Deviation?

37. Chaos Engineering
Hypothesis?
Evidence
Experiment
Steady-State Method Steady-State
Deviation?

38. Chaos Engineering
Hypothesis?
Evidence
Experiment
Steady-State Method Steady-State Rollbacks
Deviation?

39. Verification

40. Verification
Objectives

41. Verification
Measures
Objectives

42. Verification
Measures
Objectives Conditions

43. Verification
Verify
Measures
Objectives Conditions

44. Verification
Verify
Measures
Objectives Conditions
Im
pact on…

45. Verification
Verify
Measures
Objectives Conditions
Im
pact on…
Actions

46. “Verification tells you why
it’s important you explore a
set of conditions, and the
impact on something you
care about.”

47. Verification for SREs
Verify
SLIs
SLOs Conditions
Im
pact on…
Actions

48. Impact on Objectives is “Why!?”

49. Walk through

58. Summary

59. Impact on Objectives is “Why!?”

60. High Level “Decisions”
Mid Level “Orchestration”
Low Level “Conditions”
Attacks
Disruptions Activities
Turbulence
Scenarios Experiments Scheduling
Observability Safeguards
Objectives Measurements Verifications Impacts
Actions Decisions in context

61. Thanks for listening!
Get in touch to sign-up for a
free Early Access account.
chaosiq.io · chaostoolkit.org · join.chaostoolkit.org