I have a long rant about logging, but the TL;DR is: aggregated logging in general is useless don't bother, everything you need to know should be in your monitoring system. Basically, if something is broken and it's a problem, it will happen again, so you just start logging when something breaks. How do you know something breaks? Log your application metrics. Log your customer experience in the form of metrics and monitoring.<p>But don't aggregate every code exception and warning. If they aren't affecting your customer experience, who cares? And if they are affecting it, then it should be expressed as an application metric in your monitoring system.<p>Edit: To make my point a little clearer, I believe that central logging and aggregating should be available, just not turned on all the time.
Hey guys I'm one of the technical editors for the guide. We created it because logging is really valuable for troubleshooting and monitoring systems. However, it's a complex topic and so many resources today are spread around on different forums. We wanted to have a place to consolidate all that useful information into something much easier to read. If it helps a dev or ops person solve a problem faster or easier than we've done our job!<p>There is still a lot of content to be written for languages like python, ruby, and more. We'd love to have more contributors, or even just suggestions for the site. I can also get in touch with any of the authors if you have questions for them.
<a href="https://www.loggly.com/ultimate-guide/?s=parse+WSGI+logs&post_type=post" rel="nofollow">https://www.loggly.com/ultimate-guide/?s=parse+WSGI+logs&pos...</a><p>0 results<p><a href="https://www.loggly.com/ultimate-guide/?s=parse+python+logs&post_type=post" rel="nofollow">https://www.loggly.com/ultimate-guide/?s=parse+python+logs&p...</a><p>Gives you a page on NodeJS<p>Ultimate ... not so much.
'Become a Contributor' seems to mean 'please give us your email address to be added to our mailing list.'<p>This seems moderately suspect.
Loggly is crazy expensive for what they have on offer (at least given my use case which is aggregating syslog and Windows event logs). You're much better setting up Logstash or Graylog2 on-premises or in public cloud.
My four-year-old watches this show, whence I've learned all about logging: <a href="http://www.amazon.com/Mighty-Machines-In-The-Forest/dp/B00008YZ0E" rel="nofollow">http://www.amazon.com/Mighty-Machines-In-The-Forest/dp/B0000...</a>