3 ms·
I don’t understand the authors point at all >don’t use logging, use business monitoring Okay, if revenues suddenly drop 50% - then what? Where does the probl
by faeriechangling 5y ago
I don’t understand the authors point at all
>don’t use logging, use business monitoring
Okay, if revenues suddenly drop 50% - then what? Where does the problem lie and once it’s discovered how can we alert on a recurrence of the same issue and fix the issue? Presuming the underlying issue cannot be trivially permanently remediated.
The author seems to see logging as essentially making excessive alert noise inevitable when logs are meant to just be collected somewhere and scanned for exceptions known to cause incidents. Then when that exception happens at the same time revenues fall 50%… there you have it?
The authors observations are mostly valid but their conclusions just don’t make sense. The observation you shouldn’t ping an admin every time a log generates an error doesn’t mean “don’t log”
- fatnoah 5y agoThe 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.