dynaTraceMonitor HTTP 405 method not allowed
Hi,
Wonder if anyone else has encountered an issue of HTTP 405 method not allowed errors happening on "/......./dynatraceMonitor" URI and know of a workaround to resolve this? This has got to do with the UEM agent that is getting injected into all HTML pages. The specific exception for this response is that "Request Method 'POST' not supported".
Is there any setting I can change under the web server or UEM sensor configuration that will eliminate these errors?
Kind Regards
Richard
The default path for our monitoring signal is /dynaTraceMonitor. If that URL doesnt accept HTTP POSTs then I am sure your application allows HTTP POSTs on some other URL PAttern, e.g: http://yourdomain/resources/postdata. If that is the case you can go to your User Experience Management Configuration in the System PRofile and change the Monitor Request Path. Check out the following doc page - System Profile - User Experience and focus on the section JavaScript Agent.
Once you change that Path the dynaTrace JavaScript agent will POST the data to a different URL. All you really need to do is to figure out which URL Paths are able to accept HTTP POSTs
Thank you very much for the quick responses to answer:
@Roman the webserver agent is running on V5.6.0.5924 same as our dynatrace core server.
@Andreas i think the firewall that preventing the HTTP posts on that particular URL could be the case, UEM is working fine its just this URI that is appearing with the 405 respons. Should I exclude this particular path in the User Experience sensor config below? (the /....../dynatraceMonitor path?)
It could also be that the web server or maybe a firewall in front of the web server is not allowing HTTP POSTs on that URL. Thats why we allow changing the monitor path to a URL Pattern that the web app allows and accepts HTTP POSTs
Hi Richard,
Could it be that your web server agent is still using an older version? We've switched the UEM monitoring signals from using HTTP GET to POST - in your case it seems the server is getting a POST request but is not able to process it. Just wondering if a mismatch between versions could be a possible explanation here.
Best, Roman
