topic Excluding RUM JS injection by hostname in Real User Monitoring

Excluding RUM JS injection by hostname

Julius_Loman — Fri, 07 Sep 2018 10:54:29 GMT

Is it possible to exclude RUM JS injection by the hostname?

I have an application accessible via different hostnames (hostname1.domain , hostname2.domain). In the application config -> Advanced Setup it should be possible to setup rules for the injection based on

URL:However, I can't get it working for the hostname part of a URL (for the path part it works as expected). Is this just a typo and this should work just for the path?

Do we have another option how to disable RUM JS injection other than creating a new dummy application, turn the RUM off for this app and map all specific URL requests to this app?

Re: Excluding RUM JS injection by hostname

Julius_Loman — Fri, 07 Sep 2018 11:06:34 GMT

I understand it might not be possible to have the information about the whole URL at the place where Dynatrace Onagent decides whether to include RUM or not.

Re: Excluding RUM JS injection by hostname

ChadTurner — Mon, 06 Jul 2020 18:44:31 GMT

Hey @Julius L. were you able get a solution for this? The only thing I am aware of is turning RUM off at the host level, host by host.

Re: Excluding RUM JS injection by hostname

zietho — Wed, 08 Jul 2020 09:08:48 GMT

Dear all,

In theory that should work but we don't recommend doing so, since these rules were meant for excluding individual pages not whole hosts. So I'd rather take the approach that Chad T. recommends to turn it off on a host by host basis rather than using the "exclusion" rules.

Why not the exclusion rules? Because the agent uses the hostname from the headers it sees and usually takes the one from the header that is on top in terms of order in the settings. And only based on this concat URL will decide whether it injects or not.

So it might be possible with two exclusion rules but again - we'd rather recommend to use the host by host disablement than using excl. rules for this!

regards
Thomas