Ignore error 500 when http response code has a tag indicating it's a normal business condition

[reginaldo_alves]

Hi,

My customer uses OSB and It was defined in your environment the application must return HTTP Status Code 500 in normal cases of business condition error or execption. In addition, applications inserts a tag on http response header with the specific business code error.

Customer doesn't want to filter out all transactions that returns status code 500, because It's possible these transations can to indicate a real service unavailability problem.

Is there any way to configure Dynatrace to filter out and do not consider as transactions failed, when transactions returning http status code 500 come with a flag on http response header indicating It's a business code exception/condition?

I was wondering about to use the Custom Errors settings on service.

Thanks

Reginaldo

[Julius_Loman]

Never tried, but I'd say, you will have to ignore the 500 code and setup the custom error rule - If the bussiness error header does not exists -> trigger failed request.

[ChadTurner · Accepted solution]

You can exclude error codes at the service level with in the edit options on the service:

[Julius_Loman]

Well, the proper way would be to define both (he does not want to ignore all HTTP response code 500) :

• ignoring HTTP response code 500 as error
• setup custom rule to trigger a failed request if the business error header does not exist

Ignoring all HTTP response code requests is at least risky.

[erh_inetum]

Hi @ChadTurner ,

Is it possible to exclude HTTP 4XX codes from Settings > Failure detection section for the whole tenant?

I've seen it's necessary selecting and attribute and at least one MZ:

But I'm not sure if it's possible to do that for all objects of the tenant as our customer wants to.

Thanks a lot in advance,

Regards,

Elena.