I am assuming that you are using the native monitors that are in LoadRunner and not SiteScope, although depending on the way you have SiteScope set up this could be the same.
First it is important to understand how LoadRunner collects monitor data. Assuming once more that you are pulling data from Windows based servers, those monitors are dependent on PerfMon, a Microsoft provided, OS level monitoring solution.
So the first step in debugging the problem is to see if it is PerfMon or LoadRunner that is acting slowly. If you can RDP (or just walk over) to the LoadRunner Controller machine, but instead of opening the controller, open the Windows PerMon tool (Start | Run | Perfmon). This tool has the ability to monitor remote systems as well. Configure PerfMon to look at the servers over the pond and evaluate if you see the same delay.
If you do, this is a PerfMon issue. If you do not, I would suggest that you open a case with HP support to troubleshoot further.
One thing that might work for you, even if you are not using over the firewall, you could setup as if you were monitoring over the firewall. In this case you setup a Monitor over the Firewall agent on computer that is on the same side of the pond as the AUT that you are monitoring. The monitoring is done locally and the data is sent to the controller via the Listener. Even if the data is delayed, it will only impact the monitors while the load test is running. The final results you get when looking at the data in Analysis would be accurate.
Hope this helps answer your question.
Regards,
Craig Drummond
HP SW Premier Support, Technical Account Manage - ALM Products
