Logging

[awatson1978]

As per Martin:

Logging

With Bunyan or Winston, it is very beneficial and mercifully easy to not use console. (You might want to skim this comparison.) Please see these pages :

• What the stdout of generate autoconfig looks like after piping through bunyan with bunyan logging set to trace=debug
• With bunyan logging set to trace=info
• With bunyan logging set to trace=info but not piped through bunyan
• With bunyan logging set to trace=warn
• With bunyan logging left unset

If you want to review my changes to generate_autoconfig.js you will need to run :

  sudo npm install -g bunyan

[awatson1978]

@martinhbramwell

So, I was tinkering with the generate-auto config command last night, and I think we need to give a bit more thought about how Bunyan is going to be used. I'm all for using a more sophisticated logging architrcture, as I'd like to eventually pipe all my logs to a Splunk server. The problem is that people aren't necessarily guaranteed to have bunyan installed (or eslint for that matter). So I think we need to give some thought as to how those other tools get installed and configured before we migrate the entire app to using bunyan.

[martinhbramwell]

". . . aren't necessarily guaranteed to have bunyan installed . . . " Sorry but, are you concerned about the need for the Bunyan command line filter OR about adding bunyan to your package,json file?

Either way, I'm not clear on the extent of the repercussions you anticipate.