Interesting article. I have always preferred logging to a stdout stream, and having some system to capture it. However, in a cloud environment like nodejitsu or heroku, you need some control over it.
It looks like I got winston to work for me, with some real effort. Some parts of it could be a lot easier. But it is doing the job. On Monday, March 26, 2012 12:08:33 PM UTC+2, Alexey Petrushin wrote: > > Maybe it's better to just use stdout/stderr and don't mix logging > (deployment-level task) into application. Very interesting article about > this approach from Heroku > http://adam.heroku.com/past/2011/4/1/logs_are_streams_not_files<http://adam.heroku.com/past/2011/4/1/logs_are_streams_not_files> > > > On Monday, March 26, 2012 2:34:42 AM UTC+4, deitch wrote: >> >> What do people here recommend for logging? In the old Java days, I would >> use Apache commons-logging or log4j, sprinkle tons of log('debug',msg) >> statements all over the place, and raise/lower the debug level using an >> environment var. >> >> Of course, I much prefer turning it on to debug mode and connecting >> node-inspector and the WebKit interface, but that is not possible in a >> cloud-based prod environment. >> >> Thanks. >> > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
