UEM - http 503 errors
We are seeing considerable requests getting 503 and Akamai gave us the below explanation... Please let us know if you have seen similar issues...
The requests of “dt/dynaTraceMonitor” that went to the origin were all ended up with the same error ERR_CLIENT_ABORT|pump_inmem_hi=0.
Explanation of ERR_CLIENT_ABORT|pump_inmem_hi=0:
- Client closed its side of the connection before sending the POST body.
- For this error, typically, we see a 0 in the f-record to origin, and usually a 503 error served to the client, with the error description above logged in the f-record.
- One possible cause might be related to the header “Expect: 100-continue" (compatibility issue with the POST and SureRoute). Please verify if such header exists in the request and remove it if possible. Otherwise, a metadata change might be required.
Hi
This request is sent by the dynaTrace JavaScript Agent. You need to make sure that this request ends up on your Web Server where the dynaTrace Web Server Agent is installed. The easiest to test this out is if you open your browser and test the url, e.g: http://yourwebsite.com/dt/dynaTraceMonitor
In the dynaTrace Client you can also use the UEM Health Check feature to test your settings
This is happening for only few percentage of the requests but considerable enough for Akamai to let us know. Our logs don't show a 503 being generated for the Rum requests.
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 