In this article, I will explain the steps involved in sending BizTalk tracking data/trace details to Azure Application Insights.
Lets create an instance of Application Insights in Azure portal as shown below,
Make sure you Download the BizTalk Server 2016 Feature Pack 1; this update enables BizTalk to integrate with Azure Application Insight. Once the feature pack is installed, we can see a section called “Analytics” in BizTalk Group hub settings page.
Once the analytics is configured at the group level, now we can enabling tracking at individual artifacts level, as shown below.
I have enabled the Analytics for send port, receive and orchestration. This ensures that all the data will be pushed to Application insights. From Application Insight azure portal; You can explore these metrics and create graphs for data visualization; once the data is pumped to Application Insights.
This is my simple orchestration, which would send the trace logs to application insight using the helper class.
As you can see the logs are available under traces.
Lets create an instance of Application Insights in Azure portal as shown below,
- Log on to Azure portal and add a new application insights instance and Provide an appropriate name.
- Choose application type as General.
Make sure you Download the BizTalk Server 2016 Feature Pack 1; this update enables BizTalk to integrate with Azure Application Insight. Once the feature pack is installed, we can see a section called “Analytics” in BizTalk Group hub settings page.
Once the analytics is configured at the group level, now we can enabling tracking at individual artifacts level, as shown below.
Below are few pointers on AppInsight logging mechanism for BizTalk.
- Captures analytics on BizTalk Message Box only.
- Context Properties available on messages are captured in App Insight.
- For Physical Ports 2 entries are made (Receive and Send | Publish Subscriber)
- For each logical Port, an entry is made (Orchestration)
- There should be a dedicated Send Port for routing exception message to capture exceptiondetails in App Insight.
- Analytics can be captured at Ports and Orchestrations. It’s not mandate to enable tracking at ports and orchestrations; enabling analytics is sufficient.
- Orchestration entries are captured with respect to logical ports. If call or start orchestration doesn’t have any logical ports; analytics entries for these orchestration aren’t captured.
This is my simple orchestration, which would send the trace logs to application insight using the helper class.
As you can see the logs are available under traces.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.