topic Re: Deal with HTTP 500 Internal Server Error as an controlled errors in Alerting

Deal with HTTP 500 Internal Server Error as an controlled errors

jcamps — Wed, 12 May 2021 10:34:09 GMT

Hi all,

we've one application sending HTTP 500 Internal Server Error when we are dealing with a controlled error.

This is a common bad practice but this application is consumed by several clients and is not so easy for us to change the behaviour.

Dynatrace raises problems for these HTTP 500 Internal Server Error (as usual) but they are not "real" errors.

So, there's any option in Dynatrace to obviate these HTTP 500 Internal Server Error in the problems and not raise problems in this kind of HTTP 500 Internal Server Error (maybe based on some exceptions or messages)?

Regards, Josep Maria

Re: Deal with HTTP 500 Internal Server Error as an controlled errors

JamesKitson — Wed, 12 May 2021 12:49:35 GMT

In the error detection settings for a given service you have some options. One option is to change the HTTP status code settings to not consider 500s an error but odds are you don't want this if it is only certain cases where the 500 is 'controlled.'

I think your best bet is to see if you can find the underlying exception that causes the 500 to be sent and then add it as a 'client abort' exception. This is like 'ignore exceptions' but will also override error status codes being returned. Basically, if we see such an exception that PurePath won't be marked as failed no matter what.

https://www.dynatrace.com/support/help/how-to-use-dynatrace/transactions-and-services/service-monitoring-settings/configure-service-error-detection/#expand-client-abort-exceptions-2334

Re: Deal with HTTP 500 Internal Server Error as an controlled errors

jcamps — Wed, 12 May 2021 13:05:43 GMT

Thanks, good solution!