title: .Net Web Service Logging
body: <p>My ideal situation for logging in our web service would be to log all the method calls (authentication as well as data access) with the parameters passed to them as well as errors that may have occured, and have them linked with a single ID that associates them with the same call.  In addition, I'd ideally like to be able to control whether all parameters are logged, or if just the method call is logged.  I'd like to be able to control if all logins are logged or just the failed ones.  Again, all information retrieved in a single request would be linked together via an id (guid or otherwise).</p>
  
  <p>This is my ideal logging situation.  If anyone knows how to implement all of this and would be willing to move to the Manchester, NH area... ;)</p>
  
  <p>But seriously, does anyone know how I would go about tying a webservice request received to an error, or method call?  My initial attempts involve messing around in a Soap Extension, trying to add a header (soap or html) and what not to pass an arbitrary value from the extension into the service itself.  All my attempts have not succeeded.</p>
  
  <p>Our current logging situation has the authentication logging to one table, the method/business calls to another table, and exceptions logging to another table, with no interconnection between them.  Timestamps are helpful, sometimes, but not reliable enough to effectively debug.  We're currently on .Net 2.0 with the potential to be using 3.5 by the end of the year, so it would be more helpful if replies were kept to 2.0 functionality.</p>
  
  <p>Anyone got any ideas?</p>