Finding the Root Cause of a Problem
In order to determine if something is wrong it is best to know how the system is supposed to work. In the computer business this is spelled out in a Requirements Document. The document goes into great detail on functionality, how it's supposed to work, who's supposed to use it, and what task it is made to accomplish. A good Chaos Engineer will read the document and write up a list of tests, to make sure it works as designed. But the Engineer doesn't stop there. They also write up tests for compatibility, stress, negative, and errors. The Engineer thinks up ways to exercise the system in ways that it will break. If the system does indeed break, the issue can then be reported and fixed before the product is shipped out to the customer. In fact, it's much cheaper to fix the problem before it gets to the customer than after. Yay Chaos Engineers! If there is a problem, then it's good to look at the symptoms and look for a main cause. Better to find the cause and fix ...