I recently read Julie Lerman's column in the August 2012 issue of MSDN magazine. (OK, I'm a few issues behind <g>). It was on the topic of logging and was kind of scary about what can happen if you don't design it right. A 5800 line SQL query generated by EF!

http://msdn.microsoft.com/en-us/magazine/jj553510.aspx

>The problem with logging is that it's rarely done in a way that's exensible and doesn't add overhead to the system. There are ways to log that don't add alot of overhead, but how you do it depends on why and what you log.
>
>>I decided to move the logging part back to the caller. I am logging in the text file string like this
>>
>>"Calling Remote ModifyPass On {0} with: {1}", ip, invokeString