Hi Mike,
Can you check that Windows Firewall is not blocking comms between the Gateway and the Engine? A simple way to do this is to logon to the RUM Engine web console from a browser on the Gateway server, and also try to login to BSM from a browser on the RUM Engine. If either don't work, check the Windows firewall settings on each server.
I am using a test APM 9.50 / RUM 9.51 environment, and left the Windows Firewall active on the Engine so could not run reports that get data from the RUM Engine database.
Also, check the following metrics in the RUM Engine web console System Health page:
Drill down to the Probe, and then Probe Channels Status and look for Action Hits...
Probe Action hits - shows the number of hits per second for all RUM apps on that Probe. If this is zero, then the Probe is not seeing traffic matching the RUM applications
Probe Action Hits Published by BBRetriever - shows the actions per second that the Probe is publishing to the Engine. If this is 0, but you have action hits on the previous metric, it shows that the Probe is not publishing data
Probe Action Hits Read by Engine - this shows if the Engine is picking up the data from the Probe or not. If this is zero, but the Probe is publishing data, then you could have a comms issue between the Engine and Probe, or a problem on the Engine
If these are all OK and showing similar values, check the following:
Go back to the Parent View and go to RUM Engine, then BBRetriever Information and check Total Actions Published and Read
Then go back to the Parent View and go to Samples to Application Performance Management... and check for Total Samples Created (shows the Engine is processing data...) and Total Samples Sent (...and sending data to APM). Also check that Publisher Samples Thrown is zero - this is where the Engine is dropping data.
If that all looks OK, then it could be a problem on APM.
Regards,
Tim
