cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

End User Monitoring (EUM)

Warning in Chrome browser while monitoring the end user performance

Warning in Chrome browser while monitoring the end user performance

I am working on a project for monitoring the end user performance of an application. Functionality wise everything is working fine, but in chrome browser when I am checking the console option in the dev tools I am getting a warning message. The message says as mentioned below -

 

(index):17 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://cdn.appdynamics.com/adrum/adrum-4.3.5.0.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
(anonymous) @ (index):17

 

After an initial research I could find that its happening only in Chrome because of Cross site Synchronous Java script getting called through document.write. Is there a way to remove this warning?

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Warning in Chrome browser while monitoring the end user performance
2 REPLIES 2
Cody.Naumann
AppDynamics Team

Hi, I think this article might have a way to workaround that error: https://community.appdynamics.com/t5/Knowledge-Base/How-to-troubleshoot-issues-around-adrum-js-invok...

 

@Gaurav.Soni please confirm. Also, the error message is formatted strangely, probably want to fix that. Thanks.

thomas
New Poster

Encountered the same issue as OP. The suggested workaround worked for me.