Vice Admiral Vice Admiral
Vice Admiral
721 views

No RUM sniffer probe data in APM (BSM) application health - Need Help

Hi,

I am new in APM(BSM) & RUM. I am not able to view RUM probe (sniffer) data in APM (BSM) application health. No data in any report. Probe is working fine, RUM health is ok, configurtaion is fine. screen shots are attached kindly have a look.

Kindly help.

Best Regards

Labels (1)
0 Likes
14 Replies
Micro Focus Expert
Micro Focus Expert

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

Vice Admiral Vice Admiral
Vice Admiral

Hi Tim,

Thank you so much for your help. I really appreciate your support.

All firewalls are disabled.

Actully, now i can see the RUM data in APM, problem has been solved. Issue was with jmx console password, so APM was not able to get the data.

Menthioned 3 actions hits data is 0.

But these action hits are showing 0 in RUM web console.

Why the values are 0 now?

Sharing screen shot with you.

Kindly have a look.

Menthioned 3 actions hits data is 0.

Total Actions Published and Read are also showing 0 value.

Total Samples Created  0.1 samples / second (6318 samples)

 

Total Samples Sent  0.2 samples / second (6312 samples)

But, APM is showing RUM data in application health.

Now please suggest me what is going on. Where the actual problem is.

Regards,

Mike

0 Likes
Micro Focus Expert
Micro Focus Expert

Hi Mike,

Action hits will be for actions you define in the RUM configuration for that RUM app in APM, End User Management.  Therefore, this is expected if you have not defined any RUM Actions yet.

Regards,

Tim

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.