@diosmosis opened this Pull Request on January 17th 2019 Member

Instead of Common::printDebug that always prints w/ DEBUG log level and only if tracker debug is on, use the logger directly so error logs will show up in the file logs at least.

I changed some of the printDebugs for errors to error logs so the full stack trace will appear in the file logs, and so they can be potentially combined w/ the fingers crossed handler.

Test scenarios:

  • normal tracking default settings (no error / error)
    No error: no logs
    w/ error: logs in file not in response
  • no tracker debug, debug level log (no error / error)
    no error: debug logs to file, not in response
    w/ error: debug/error logs to file, not in response
  • tracker debug on, warn level (no error / error)
    no error: prints debug logs to response + file
    w/ error: prints debug logs to response + file
Powered by GitHub Issue Mirror