“Do not log specific things, just pay for a service that logs everything” The false dichotomy between monitoring and logging here is so bizarre, they’re not mu

“Do not log specific things, just pay for a service that logs everything” The false dichotomy between monitoring and logging here is so bizarre, they’re not mutually exclusive. When an alert wakes you up on a weekend, having a log statement with useful context is not going to kill you... Also: > Isn’t it a bit too hard?! Look, I just want to write strings into stdout. And then store it somewhere. So do that? Why is the author pretending you need to use ELK stack? And what about their example is “too hard”, if you’re deploying your own application that’s the least of your complications, and if you aren’t and already paying a premium for it, there’s plenty of managed ELK and ELK-like products (and I’d also be surprised if your managed deploy platform doesn’t already support you just logging to STDOUT)