There could be various reasons why you are not seeing the throttling data in the BizTalk360 throttling analyser. The following check list can help you identify the issue:
1. Make Sure BizTalk360 Monitoring Service Is Running Without Any Errors
BizTalk360 monitoring service is responsible for collecting the BizTalk host throttling performance counter(s) values. So, health of the monitoring service is very critical for collecting the data. You can verify the health of the monitoring service by navigating to Settings > BizTalk360 Health > Monitoring Service Status.
2. Make Sure BizTalk360 Monitoring Service, Account Has Administrator Rights On All The Machines In The Configured BizTalk Environments
In order to collect performance data from a remote machine, the account should have administrator rights on the machine. There are other fine grained options, but BizTalk360 only supports having administrator rights on all the configured servers.
3. Make Sure BizTalk Host Meets The Following Conditions
- Handlers are created for the Host
- Host Instances are created for the Host
- InProcess host instance is in running state
- Isolated host instance is loaded
4. Make Sure Performance Counters Are Not Corrupted In Your Environment
On some occasions, performance counters get corrupted and there are few options to restore them back as explained in the following article - http://blogs.digitaldeposit.net/saravana/post/2011/12/09/Missing-BizTalk-Performance-Counters.aspx
5. You May Need To Restart The Monitoring Service
When you restart the host instances, you may also need to restart the BizTalk360 monitoring service. There is a known challenge as explained here - http://support.microsoft.com/kb/922775. Perfmon (in our case it's BizTalk360 monitoring service) does not detect when a managed program restarts on the remote computer. This issue occurs because the Remote Registry service runs under the Local Service account. The Local Service account is not a member of the Performance Monitor Users group or of the Performance Log Users group. Therefore, the Local Service account does not have access to the CLR performance counter IPC block. Nevertheless, you can monitor CLR performance counters because the Remote Registry service impersonates the user who initiated the monitoring.
However, if the monitored process restarts, a new IPC block is opened by an auxiliary thread in the Remote Registry service. This auxiliary thread does not impersonate the user on the client. Therefore, the thread cannot access the CLR performance counter IPC block. To work around this issue, restart the performance counter monitoring from the client.