The point is that the domains/URLs have already been transferred to the new application, however, for the time when they belonged to the Default Application the data will have been visible in it. The new data after the transfer, is already in the target application.
If you change the time range on Timeframe Selector to when the domains were already assigned to the correct application, this information should disappear.
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!
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.
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.