Is it possible to get more information on why 3rd party script failed?
Hi all,
New Dynatrace user here, we are just trying to figure out an interesting issue,
Time to time Dynatrace (SaaS) will raise "problem" alert due to increase rate of JavaScript errors in RUM (Real User Monitoring) part of the application.
For most of the cases we are able to see which script caused the issue and what's the error message, then we can take action and fix it.
However there are rare cases where only thing we can see is "Script error". (screenshot #1)
We can see that it's 3rd party but it's still concerning since any JS can break the page looks or the flow, especially our 3rd party A/B testing or ads scripts.
When we drill down to above item, below is what we get. (screenshot #2)
"Script file information not available due to security constraints enforced by the browser for JavaScript from 3rd party domains."
Problem is, when I visit the same page with different browsers, I cannot reproduce any 3rd party JS errors. There is an ad script which is causing CORB error on the page but I'm not sure if that's all there is to it. Maybe there was indeed a JS error on the page, not just CORB. (Scripts introduced by GTM are dynamic, can be added/removed/modified via development or deployment.)
Even if it's CORS/CORB error, it would be good to know if there is a way to see which script's request (XHR or fetch) caused the issue for requesting which resource. I can see the CORB error right now but last time I checked, it wasn't there.
I'm wondering if there is a way to work around this and get the necessary info or whether this is something which can be added as an enhancement to the Dynatrace platform.
When you go down on this script, you should see button "Upload minified file". You can download script by your own, upload it to DT and you should be able to see place in code which makes issues.
Sebastian
Thank you for your answer @sebastian k.
I'm still looking for a way to see the error details for real users.
I have a feeling there are device/browser combinations out there - which we are not "QA"ing with - encountering these issues.
If dynatrace is not able to show you this I recommend you to use fiddler pared with your mobile device. You will be able to see error details:
https://docs.telerik.com/fiddler/Configure-Fiddler...
Sebastian
