Logging and tracing in BizTalk can be achieved by using Log4Net or DebugView in combination with System.Diagnostics.Trace
or System.Diagnostics.Debug
. Previous recipes have shown these options. Both can be used, but do not deliver the desired level of agility and performance according to research conducted by the Application Server Group ISV Partner Advisory Team (http://blogs.msdn.com/b/asgisv/archive/2010/05/11/best-practices-for-instrumenting-high-performance-biztalk-solutions.aspx). Their findings were as follows:
High CPU utilization while using DebugView when monitoring BizTalk applications
High impact on application performance when running DebugView during stress testing
Burden on the administrator to restart BizTalk host instance when any changes in the tracing configuration such as enabling, disabling or changing the trace level were required
Log4Net and DebugView are not good options to use in production environment when performance is...