The .NET Framework’s standard System.Diagnostics.Trace component is often being used for instrumenting .NET applications but when event capture is enabled in the DebugView tool it significantly impacts application performance. Therefore it’s not suitable to use in a production environment. If you want to use tracing in all your environments you can use the BizTalk CAT Instrumentation Framework. It’s is a high performance tracing/logging framework for BizTalk that builds upon the Event Tracing for Windows (ETW) infrastructure. Microsoft used essentially the same framework to instrument BizTalk itself, as well as many recently released adapters.
You can use ETW tracing in regular BizTalk artifacts but also in custom ESB Toolkit components it’s possible to implement it.
Instrumentation of Itinerary Messaging Services Itinerary Messaging Services can be instrumented using TraceManager.PipelineComponent which is dedicated for this type of BizTalk artifacts.
Instrumentation of Itinerary Orchestration Services As Itinerary Orchestration Service can be complex, the instrumentation is becoming a key factor in helping to diagnose and troubleshoot behavioral problems, performance-related issues and other bottlenecks that were not foreseen or manifested themselves during development.
Instrumentation of Custom Components Custom .NET components that are executed in Itinerary Services can be instrumented by invoking the trace methods provided by TraceManager.CustomComponent
The examples below illustrates how to use the TraceManager component inside an Itinerary Orchestration Service.
When you trace to file you can open the file in a Text Editor by clicking on the “Open Log in Text Editor” button.
For more information on ETW tracing see: