4 ms·
I have never regretted taking the time to make sure my projects have a proper logging infrastructure with every possible thing fed to the logger. I've built log
by amyjess 9y ago
I have never regretted taking the time to make sure my projects have a proper logging infrastructure with every possible thing fed to the logger. I've built logging support libraries to set up AOP hooks to auto-log the call stack at all times, and it's been a lifesaver.
I can't imagine not over-architecting this kind of stuff. I know I'd be in a world of pain several times if I hadn't.
- cpfohl 9y agoIf you would have been in a world of pain, I'd argue you weren't over architecting. You were doing your job just right!
- tokenizerrr 9y agoHow do you prefer to store/ship logs?
- eropple 9y agoNot 'amyjess, but the rightest answer I've found (and I do a lot of this stuff) is to use a Bunyan-style one-JSON-object-per-line log file and ship to something that can consume it (ELK, CloudWatch Logs, whatever). AWS CWL is dirt cheap and the awslogs daemon, while pretty far from perfect, does work pretty well. You can also couple it with CloudWatch Metrics.
- marcosdumay 9y agoThat's completely dependent on the format of your infrastructure. There is no answer that will fit everybody, and asking around for advice of strangers may even bias you in a damaging way.
- tokenizerrr 9y agoOf course it is. I am familiar with all the common methods, but I'd like to hear how other people solved it for their specific situation.