You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to extensively track issues as they occur on production, so we will want to set up a better logging system then our current one (console.log/error). Bunyan looks promising. https://github.com/trentm/node-bunyan
The text was updated successfully, but these errors were encountered:
I think we should push off this issue for now, until after we have real users on the system. Our current console.log system is not perfect, but Logentries is doing a good job of detecting crashes and should be good enough for the demo.
I've been playing around with node-bunyan on another branch (colin/bunyan), and it looks promising for providing more data when crashes do occur, however it comes at the cost of readability during development (It's built to be parsed afterwards). We can write some small serializers to improve this, but this will be easier to do once we have a better feel for the kind of data we do want in our logs.
colinking
changed the title
Set up Bunyan logging
Improve logging system
May 22, 2016
We want to be able to extensively track issues as they occur on production, so we will want to set up a better logging system then our current one (console.log/error). Bunyan looks promising. https://github.com/trentm/node-bunyan
The text was updated successfully, but these errors were encountered: