Type-safe model-based alerting
Alerting is something you must do well. You cannot fix what you do not know about, and understanding your system well enough to know what anomalous behavior looks like is a fundamental command of any software developer working in a system that is sufficiently complex. Despite the prerequisite required knowledge of the component/code/behavior, there is an implicit requirement to also understand the statistics behind your model-based alert. Regardless of how you have implemented your alerting, you are using a model to predict or outline divergent behavior.
About
If you see fraud and do not say fraud, you are a fraud. – N. Taleb There are countless misconceptions in the world of distributed software systems. I am not a theoretician, I am a practitioner with an interest in solving problems the right way. With those caveats, let us dive in. This blog is intended to drill down into how to manage risk in distributed software systems.