What steps will reproduce the problem? 1. Run any unit test 2. 3.

No logging is currently performed, but I would like to see logging from the transports.

Integrated log4net.config into test project.

Still need to add logging to components in .ServiceBus

I will look into adding Castle.Core ILogger into every component.

Looking at creating a special log formatting for message tracing apart from the regular logging in order to troubleshoot issues at a level slightly above DEBUG.

Example?

FATAL ERROR WARN INFO DEBUG

These are not sufficient? That's totally cool. What about using the NDC stuff?

NDC?

I think INFO would be good for messages being put onto and taken off the queue. Right now there is a lot of extra information.

I'd also like to come up with a formatter for the queue interactions that is easier to visualize in a log viewer to see the in/out transitions.