topic Re: RUM:How does the beacon work ? in Real User Monitoring

RUM: How does the beacon work ?

gautier_begin — Fri, 10 Mar 2023 11:20:59 GMT

Hello,

Could you explain how the beacon is running, ie how the RUM monitoring data are sent back to the OneAgent after collection of information by the JSagent. Is there a kind of virtual web API on the monitored application put in placed by the OneAgent?

What's the network flow and URL that is used to send back monitoring data ?

Which kind of configuration can be made on this feature, to fix which kind of issue ?

Regards,

Re: RUM:How does the beacon work ?

nj_njoku — Wed, 07 Mar 2018 23:36:47 GMT

Hi Gautier,

The RUM monitoring data is sent back to whatever URL you configure as the beacon in Application->Edit -> Advanced Setup -> JavaScript Library -> "Specify path where JavaScript tag should send monitoring data" as a POST request. If no URL is configured in that field, you will see a POST request that begins with rb_<ID> in your browser's developer tools where ID is your Dynatrace environment ID. E.g if RUM is enabled on your website https://www.mywebsite.com the Request URL of the POST request will be https://www.mydomain.com/rb_<ID>. This will go to your Webserver which is already instrumented with the OneAgent and then back to the server (via SG if used). If you configure your own beacon URL, you must have some way of getting this data from wherever this URL is sending the data to back to the Dynatrace server.

Hope This Helps

Re: RUM:How does the beacon work ?

AlexanderSommer — Thu, 08 Mar 2018 06:42:55 GMT

the <ID> is not the environment id. This was changed some time ago for security reasons. It is a unique id but it has no direct relationship to the tenant (environment) id.

Re: RUM:How does the beacon work ?

gautier_begin — Thu, 08 Mar 2018 07:45:07 GMT

Ugochukwu,

We are monitoring applicatons with a contexted URL ( https:///)>/<AppContext>) and thus we are configuring by default

Application->Edit -> Advanced Setup -> JavaScript Library

with the context for both the JSAgent injection and the beacon as you mentionned it. But some time, this is not sufficient and unwanted interactions with the monitored application happens (jamming, stopping the application after beacon call,...). Do you have any advises on which configuration could help and how to diag?

Regards,

Re: RUM:How does the beacon work ?

florent_duchate — Thu, 08 Mar 2018 08:54:03 GMT

the beacon signal is sent out asynchronously so it doesn't stop, jam the application.

There are no configuration settings to change this.

Regards

Flo

Re: RUM:How does the beacon work ?

alvin — Wed, 10 Mar 2021 07:11:59 GMT

Hi Alexander,

Is "<ID>" in "rb_<ID>" still not the environment ID at this time, or it has been changed to be env ID now?

Thanks,

Alvin