Monitoring

Behaviours not Errors

Overview Recently, I have been thinking about my preference for structured logging (details on this in to-be-written entry). A trivial but significant aspect of this, is that once you have switched to structured logging, markers like INFO, DEBUG, ERROR,… don’t help. Simply grouping such a wide range of code paths into these categories is insufficient for any kind of analysis. What is an error? An error is a local failure scenario that you don’t currently understand - our continuous improvement process for error handling aims to move all these anomalies in the system from unknown to known.