Wrong mapping of successful request count with the HTTP status code

[Babar_Qayyum]

Dear All,

I noticed a wrong mapping of the successful request count with the HTTP status code in the multidimensional analysis for one of the services. What could be the reason behind this?

Regards,

Babar

[kalle_lahtinen · Accepted solution]

Could it be because 4xx responses are considered client-side errors? So by default, they do not affect server-side failure rate.

[PierreGutierrez · Accepted solution]

Hi @Babar_Qayyum 

That's kalle_lahtinen mentions is correct
By default 4xx errors do not contribute to the error rate.

Configuration default :

Something important you should know is:

Anything that is listed/configured as "server-side failure" is the only thing that will contribute to the failure rate. Therefore, anything that does NOT contribute to the server-side failure is classified as a Successful Request.

Spoiler

In case you want some specific HTTP response code to contribute to the error rate / be considered server-side failure.

I suggest you review the default configuration of Filure detection>HTTP parameters (at the global rules level or at the service level)

I hope it's helpful 💪