We came across to a issue where customer website is cloned by some hacker and serving from a new domain. As DT js also cloned, we start see data reported from these new domain in our production. Now these pages are not our pages so their low performance start impacting the our overall Apdex of application.
Is there way we can exclude specific domain from not sending beacon signal back to DT?
Hi @Shuresh K.
Did you tried to add another application detection rule with the hacked domain and put it higher then the real site ?