UEM issue with Dynatrace 5.6.0 build 5924
We configured UEM for 5.6.0 and on IE and on Chrome 37 browser we are getting exception while performing a checkout on website.
Also we are not abel to capture any UEM data in the Dynatrace.
We are not accessing any URL monitor(s) yet.
These errors are prevalent from accessing the customer web site with Chrome and most versions of IE.
The transactions fail if UEM is enabled, and work fine if UEM is disabled.
Thank you for your feedback
Hi.
It would be interesting to learn more details about these exceptions. Are these JavaScript errors? Do you have any details?
As for UEM: Please use the UEM Health Check to verify whether your UEM is setup correctly. Potential problems are that the Monitoring Signal which is by default using the url /dynaTraceMonitor might be blocked by your Web Server. For these scenarios we allow you to specify a different URL Pattern to adhere to certain restrictions. Also check the following pages: User Experience Management Administration and Firewall Constraints for UEM
Andi
Hello Andi
Thanks for your feedback
on UEM Health Check result
-dynatraceMonitor request check Response body is invalid.dynatraceMonitor URL is http://test.gymboree.com/dynatraceMonitor
I am currently working on, customer provide to me session fiddler and supportarchive
Demba
Thats what I assumed. Our JavaScript agent does an HTTP POST to /dynaTraceMonitor. If their web server configuration doesnt allow HTTP POSTS on that URL you have two options
a) they allow postings to this URL
b) they tell you which URL pattern you can use, e.G: http://test.gymboree.com/resources/httposts/dynaTraceMonitor. Then you can use this URL Pattern and configure it in your System Profile. There is a section under User Experience where you can configure the Monitoring URL Path
Andi
Hi,
What troubleshooting steps have you already tried? Is the UEM health check running through? I assume the JavaScript is injected since your page breaks - but what type of failure do you have? Is the page no longer rendering at all, is a button on the page not working? What exception do you get?
I would suggest you open a support ticket for this. Please make sure you capture a support archive and also (if the page is not accessible from the internet) the HTML of the page so they can try to reproduce UEM breaking the page. Basically everything and anything you can think of that would help our support folks to troubleshoot...
Best, Roman
