Errors happen. Things will go wrong. It’s not a matter of if — it’s a matter of when. But if we understand that fact ahead of time, we can take steps to prepare for the inevitable. Having a way to quickly identify contributing factors means we can address them faster. That translates into less downtime, which makes everyone happier.
However, knowing that you need to prepare for problems isn’t the same as having a strategy for how to identify them. If you want to be able to quickly and systematically rule things out, then you need to know what those things are, as well as their acceptable thresholds.
[ Also on InfoWorld: Devops for remote engineers and distributed teams ]
The USE method
Think of the USE method like an emergency checklist for all your critical resources. For every resource in the list, check for one or more of:
To read this article in full, please click here
InfoWorld Cloud ComputingRead More
