The author's premise seems to boil down to 1) don't have errors and 2) "simply" make sure that your APM system has sufficient context to identify what went wron

The author's premise seems to boil down to 1) don't have errors and 2) "simply" make sure that your APM system has sufficient context to identify what went wrong. Of course, both of those are pretty impossible and they ignore the similarity between creating a constant flow of information for later use (logging) and creating a constant flow of information for monitoring (not logging). I could go on and on here. The "real" point seems to be that logging should be useful and consistent, which I agree with.