Splunk AppDynamics

Warning in Chrome browser while monitoring the end user performance

CommunityUser
Splunk Employee
Splunk Employee

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?

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

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.

CommunityUser
Splunk Employee
Splunk Employee

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

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...