That's a known limitation;Are you using Angular Zone? We have some imcompatibility with the change detection mechanism in Angular apps.
When moving adrum.js in the <head> blocks the Nested HTTP Test which is why the Angular change detection doesn't kick in properly, when Adrum is included alongside. So you need to go with the workaround.
thanks for the quick response.
Further questions: is there any bug ticket you can refer to? We would like to track the state / further progress on this.
Acutally I didn't quite get the workaround. Could you please again describe what to do in order to "fix" this issue?
Actually our Angular app runs in other applications / web sites (InDom integrated) so we do not have any control about the adrum integration at all. Our application itself does not use AppDynamics, but one of the integrators does (which crashes the application).
Our requirement is that the use of AppDynamics does not interfere / crash the Angular application.
Thanks in advance.
Any updates on this (please see message from Mario)? Since this is a production blocker I really would appreciate any help. Anything else we can do, e.g. providing more information?