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.

Knowledge Base

How do I troubleshoot issues around adrum.js invoked via the document.write command?



The user has instrumented a web application with version 4.3 adrum-config.js, but they do not see the adrum beacon posted.


Opening a browser's dev tools shows the following error message:


html:51 A Parser-blocking, cross site (i.e. different eTLD+1) script,, 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 for more details.




Users who try to run the document.write command from the adrum-config.js file will fail, as the file is served from a different domain, so the browser will not allow it.


  1. To resolve this issue, one option is to use the adrum-config script inline within the head tag.
  2. Another option is to remove the document.write code from the adrum-config.js file and add the adrum.js manually via the script tag.



Within the adrum-config.js file:

window['adrum-start-time'] = new Date().getTime();
    config.appKey = 'AD-AAB-XXX-XXX';
    config.adrumExtUrlHttp = '';
    config.adrumExtUrlHttps = '';
    config.beaconUrlHttp = '';
    config.beaconUrlHttps = '';
    config.xd = {enable : false};
})(window['adrum-config'] || (window['adrum-config'] = {}));


And within the index.html:

<html lang="en">
    <meta charset="utf-8">
 <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1">
 <script src="/assets/adrum/adrum-config.js"></script>
 <script src=""></script>


Version history
Last update:
‎10-12-2018 02:33 PM
Updated by:
Labels (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.

Hi Erin, Gaurav,

This helped me a lot. however my issue was the application team had incorporated content default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; CSP policy. Therefore the above solution did not work completely.

Below is what worked out.

Add and to the content in the CSP policy as below

content="default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval';"

PLUS your changes that you have suggested.



HI Alakshya,


Thanks for pointing. That bit is covered here:



Gaurav Soni

Thanks for the reference Gaurav.