Decide on logging and error libs for golang.

[davidgwking]

Go's native error type leaves much to be desired, so I suggest we use a library to capture nice things like stack traces. I've briefly used https://github.com/jsimnz/errgo, and found it to be a huge improvement over native errors.

Logging because logging.

Here's some logging libs that I've found but haven't researched beyond the superficial scan of github: https://github.com/op/go-logging (appears well featured and documented) https://github.com/cihub/seelog (appears well featured) https://github.com/golang/glog (used this a couple of weeks ago. very bare bones.)

[davidgwking]

I implemented a logging prototype by wrapping go-logging, which all in all looked to be the better library.

Still open to alternatives as that was primarily explorative work.

[davidgwking]

I'm happy with the bootstrapping so far.

• leveraged go-logging, but provided a more robust interface that allows direct logging of not only formatted strings, but error types and structs (encoding to json) + formatted strings
• wrapped native error such that a stack trace can be retrieved and an optional context message can be stored. stacks and optional contexts are logged when passing an error to the logger.

If more work is required, further issues can be opened.