Resource errors should include response in log #8
Description
Working on a project that had a misconfigured API key, this was the feedback I got loading a page with loglevel 3:
[2015-04-13T19:21:39.451Z] 2 /tour [upcoming] Resource error: Invalid data status
That's not too informative. It'd be helpful to see the response in this scenario in the log and perhaps hte context as well. Any JSON responses would need to be prettyprinted to be useful, but that could be a problem in a production log. Perhaps the current behavior remains as-is for production and these enhancements are a dev addition.