Looking in my default application, it shows Domains that included the message "transferred to" and then it shows the correct application.
This means that I have applications/useractions in both correct and the default application
What could be happening here?
Solved! Go to Solution.
This looks like a bug, because if you do the 'Transfer' option to a new application, the data should start collecting at the destination.
Have you tried manually defining the application from the settings tab?
Thanks for your hints and advise, created rule is perfect. We tested this on an other enviroment and there the "transfered to" and application(s) were removed from the source.
I agree, it must be a bug. I have create a ticket for Dynatrace and will let you know the outcome!
Thanks for your help.
I've seen this issue when a CDN or a proxy/service mesh are involved.
The rule the transfer tool creates only uses the domain name as it appears in the UI in the default app, typically the public DNS name (ex: myapp.com). However, if your app is behind a CDN or a envoy proxy, the public DNS name may not match where the data is served behind those resources (it might be coming from backend.my-backend-domain.com). So the rule never matches and it still "falls through" to the default application. The fix is creating an application detection rule to match the backend domain name with the desired Application.
My walk of shame...
To put it simple, there were no requests for the Domain in the detection rule,from oneAgent perspective. So all "transferd to" wiere stuck there forever waiting for the fist request.
Thanks to Adam (dynatrace support)->
Check the user actions in the Default app -> get the web requests visible in the waterfall -> goto the transaction trace -> look in the request headers.
In my case there was a DMZ messing things up )-:
I still do not know how I missed that,