Monitoring

Agile and DevOps have pushed faster and more frequent releases. Techniques like integration test, feature flags, canary tests, and monitors evolved to maintain service reliability without slowing that pace. But some code paths are so critical that they cannot fail even once. This is where Scientist comes in.

This post is mostly a self-reminder to think more on a few logging ideas I encountered. I figured others might benefit from them too.