At times, the process monitoring may not be working as expected - say, for example, you would have processed lot of messages during the time frame, but the email notification would mean the opposite - a false alert saying there were no messages during the time frame. We suggest that you ensure the following prerequisites are met to avoid these kind of situations.


1. Make Sure The Tracking Setting Is Working As Expected

BizTalk360 process monitoring basically relies on the BizTalk server tracking data to calculate the transaction volume. As a design principle, we do not want customers to deploy any custom stuff (like pipeline component, pipelines, BAM artifacts) etc and wanted to take advantage of power of BizTalk server. So, in order for the process monitoring to work correctly, the tracking setting in the environment must be working correctly. You can easily check whether the events are captured correctly by executing the following query in the BizTalk Admin Console (with your required settings).


 

If the result of the above query returns no results, then you have some tracking configuration problem. Follow the next set of prerequisites to solve this problem.


2. Make Sure Global Tracking Is Enabled In The Environment

You can do this by checking at the BizTalk Group Settings as shown below:


 


3. Make Sure Event Tracking Is Enabled At The Pipelines Utilized By The Corresponding Receive & Send Port

For example, if you are using PassThru pipeline, you can check the following check boxes are enabled:




4. Make Sure At least One Tracking Host Instance Is Running

From the below picture, we can see BizTalkServerApplication is the tracking host. We need to make sure at least one host instance is running for this host.