Apdex relation with 4XX and 5XX error rates

Hi Team,

We have a condition for a policy for Apdex, where we have used 0.85 as the default threshold.
As per New Relic documentation only 5XX series of errors should be responsible for reducing the Apdex being calculated.
We have a service which has only 401 series of error(almost equal to the number of transactions). This as expected does not results in a higher response time. The average response time for the service is still below 35ms with T=0.5. However, the Apdex is 0.7 where as ideally it should have been very close to 1.

Could you please clarify on the below queries:

  1. Does New Relic by default consider client side errors as frustrating response while computing Apdex?
  2. Is there any other way apart from marking 4xx errors as expected to exclude it from Apdex computation if [1] is true.
  3. If [1] is false, then we need to know what else could be the reason for low apdex score since, response times are way beyond the Apdex T and there are very minimal number of server side errors.

Hi Team,

This is in relation to the discussion post : https://discuss.newrelic.com/t/apdex-relation-with-4xx-and-5xx-error-rates/126205

We have a condition for a policy for Apdex, where we have used 0.85 as the default threshold.
As per New Relic documentation only 5XX series of errors should be responsible for reducing the Apdex being calculated.
We have a service which has only 401 series of error(almost equal to the number of transactions). This as expected does not results in a higher response time. The average response time for the service is still below 35ms with T=0.5. However, the Apdex is 0.7 where as ideally it should have been very close to 1.

Could you please clarify on the below queries:

  1. Does New Relic by default consider client side errors as frustrating response while computing Apdex?
  2. Is there any other way apart from marking 4xx errors as expected to exclude it from Apdex computation if [1] is true.
  3. If [1] is false, then we need to know what else could be the reason for low apdex score since, response times are way beyond the Apdex T and there are very minimal number of server side errors.

Please find the below links for the service:
Insights: NRQL link
Incident: Incident 202927740
Newrelic: Error Count

Hi team
Any update on the above.
@philweber

Marking this discussion as resolved. have got the required confirmation on the request ticket below
https://support.newrelic.com/tickets/441747/edit

Hi Bikash,
Can you provide the information in this post? the ticket looks private and I’m also very interested in their answer. :pray:

Hi, @nico.sommi: Here is the response from the support ticket:

  1. True. We do consider client side errors in marking transaction as Frustrating. We can see here in this unit test that we expect a 401 to be marked FRUSTRATING
    https://github.com/newrelic/newrelic-java-agent/blob/02888f92137ac045ed0d72b1e645e7e4da4d8958/newrelic-agent/src/test/java/com/newrelic/agent/stats/ApdexPerfZoneDeterminationTest.java#L35

  2. Expected and Ignored errors are the only way.

The expected errors config was designed for the case where you want to report the error, but not impact Apdex.

1 Like