Logging was always a nightmare for me! Now I have to implement it again for a proxy system.In this proxy application, some systems ask proxy system to call some other services.What I have to log isRequest TimeRequester IPRequest Parameters as XMLRequested Service NameRequested Service MethodResponse TimeResponse data as XMLResponse Message (If any exception occurs it will logged as Message)I considered to append two lines to my methods:// Log RequestTask.Factory.StartNew(() => Logger.Log(RequestParameters.ToXML(),Assembly.GetCallingAssembly().FullName, MethodBase.GetCurrentMethod().Name, DateTime.Now));// Invoke requested service and get response// Log ResponseTask.Factory.StartNew(() => Logger.Log(Response.ToXML(), DateTime.Now));I also want to log nested transactions.Assume a transaction contains a request and a response. A transaction may contains many other internal transactions. When I receive a request, I should register a transaction, and insert a request for it, later, when response received, I should update the transaction response. Please note that I'm trying to store request and response relationship for better tracking.How can I safely add this logging procedure to methods? I want to restrict developers to implement this logging systems in all methods, some thing like interface or inheritance for method body is required. Can I do this by attributes? Then how? 
Log design approach
c#;design;object oriented design;logging