HNHacker News
TopNewBestAskShowJobs

kfsdfjdf

16 karma · joined January 5, 2022

submissionscomments
kfsdfjdf··on Do Not Log
That's true. Annoying and pointless logs at least tell you where they are :). I suppose what I meant by this is in the heat of the moment having to sift through overlogging probably somewhat justifies the "no log" rant on the surface. But the underlying problem isn't logging but rather the abuse of it so it seems a little premature to blame logging itself for this.
kfsdfjdf··on Do Not Log
I have no idea what the authors qualifications are.

There have been uncountable cases where a GOOD log trail has been the difference between a 20 hour journey through a code base and a short stop to immediately discovering the problem. Common failure points should be logged, especially when they are deeply nested, or they involve complex hard-to-diagnose processes.

Overlogging is just as bad. But to say "do not log" and then suggest using services like sentry or datadog instead is really reaching around your nose to touch your face. You're doing yourself a disservice by lacking the final bit of correlation - the approximate location and nature of the failure. There have been times when I've been on a service so complex that just building a harness to reproduce the case takes hours or days. Not everything is a nice, clean, small and simple microservice where you only have N guesses at where the problem could originate. On a large enough, or old enough, service the upper bound could approach N! very quickly.

I'm not sure why this was posted to HN as it seems like a very low-quality ranty post by someone whom I'm not sure has ever worked on a large enough project where it becomes non-obvious what the origin of some error alerts are.