When you install the .NET Agent on a Microsoft BizTalk Server, the agent automatically discovers BizTalk entry points and exit points so you can monitor your BizTalk integration.
- Microsoft BizTalk 2010, 2013
- BizTalk must be a downstream tier from an originating tier for a business transaction. The agent doesn't discover BizTalk as the originating tier of a transaction.
The .NET Agent detects incoming BizTalk requests using the WCF Send Adapter or the SOAP Send Adapter.
Instrument the BizTalk Service
- Install the .NET Agent on the BizTalk server. See Install the .NET Agent for Windows.
- Register the "enable-soap-header-correlation" app agent node property with a value of "true" for the nodes upstream from the BizTalk tier. See App Agent Node Properties.
Instrument the BizTalk service executables: BTSNTSvc.exe and BTSNTSvc64.exe. See Configure the .NET Agent for Windows Services and Standalone Applications. For instance:
If you run multiple instances of BizTalk on the same Windows server, you can assign the different instances to unique nodes using command line options. For example, to differentiate nodes within the same tier, specify the BizTalk Service command "name" parameter in the standalone application
Notice the use of quotes to enclose the name command-line parameter.
Optionally enable BizTalk performance counters. For more information, see Manage Windows Performance Metrics. Refer to the Microsoft BizTalk Server documentation for descriptions of individual performance counters.
Once you've completed instrumentation, the .NET Agent correlates traffic through your BizTalk server:
If you enabled Performance Counter metrics, they appear under the Custom Metrics tree in the Metric Browser.