More detailed logging about colossus HOT 1 CLOSED

This is an older issue, which we've been punting on for a while.

The bullets are:

• Logging in Colossus is not very complete, only a few components have some level of logging
• These classes tend to be Actor based, and use Akka logging for their logging
• There are a lot of components, which are not Actor based and hence do not use logging, since using Akka loggers outside of Actors feels a bit clumsy(my own thoughts)
• Personally, I've always felt somewhat annoyed that I have to manage 2 different logging parameters when using Akka(ie: akka log level and an SLF4J level as well)

Possible implementations:

• Use SLF4J loggers exclusively, even within Actors. This addresses the bulk of the points above. We could just include SLF4J and use it within non Actor based components, but I'm not a fan of mixing logging systems like that.

• Akka logging does have nice call by name parameters, which will lazily evaluate log messages. I like that, and we could create our own Logging trait(similar to what we have here internally). This Logging trait could just wrap an SLF4J logger, and we could then use that throughout the framework

  We still need to talk about what we want to capture at each level. However, this ticket can be broken into many smaller tickets:

• swap to SL4J, create basic Logging harness, swap all existing logging over to this

• ticket for each major component/layer that needs some logging love.

from colossus.