20 Jul 2021 03:49 PM - last edited on 28 Mar 2023 09:19 AM by MaciejNeumann
Hi Community
I have a query related to RUM. We want to bring in the RUM traffic to our CAG directly rather than routing though web host.
I see we have a option in Advance Setup and its working well and we see traffic reduction on our Web Host with this.
I am looking to know if we have a way to mask the environment id that we need to supply in these setting because we don't want to expose our id to our users.
Please let me know if there is a option.
https://<dns-CAG>:<port>/rb_<environmentid>
Thanks
Solved! Go to Solution.
20 Jul 2021 04:31 PM
The environment ID is needed so Dynatrace knows to which environment the beacons belong.
If you don't want it visible in the browser you use a load balancer or reverse proxy between the browser and cluster AG to which the beacons will be sent. The load balancer / reverse proxy can then rewrite the URL to the correct one, for example based on the domain of the request.
20 Jul 2021 07:27 PM - last edited on 28 Mar 2023 09:22 AM by MaciejNeumann
hi Pahofmann
If we setup a LB (example : https://rum-resolver ) and on our LB we set this to resolve to CAG (eample : https://<dns-CAG>:<port>/rb_<environmentid> )
Can we be able to supply the LB resolver in JavaScript Library and in the incoming request will be able to reach to us back as expected please.
Thanks
20 Jul 2021 07:50 PM
Yes, you would enter the full URL to the LB in the application settings as the (cors) beacon URL.