HTTP status codes 970-979

[AntonioSousa]

I have an application that started showing a lot of HTTP/971 error codes. Never had heard of these HTTP codes, looked online, didn't find anything.

Then I found in the UI that it referred to "Canceled". After some more searches, found a page in the documentation, in that these errors are specific to Dynatrace RUM 🙂
https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/setup-and-configura...

They are the following:

They can be configured to not affect Apdex, which they do by default in Applications created after version 1.238

[ChadTurner]

Great Tip! thanks @AntonioSousa 

[nrodrigu]

Hello Antonio. So does that mean that these codes can be removed without problem for Apdex issues?

[Romanenkov_Al3x]

As always, I also got this exotic. Does anyone know some undocumented JS agent flags like cux = 0 that could help in this case and remove this status codes from application\affecting application?

Customer faced with problem that these JS codes impact on customer "best frontend code ever".

Regards,

Alex Romanenkov

[Julius_Loman]

@Romanenkov_Al3x Did you remove them from the error detection rules for the web application?

[Romanenkov_Al3x]

Hi Julius.

I have already removed this rule, but it didn't help. Customers code works only without JS agent loaded on page. Problem related to file uploading when agent is injected and customer code look like works without "No response" http codes.

Dynatrace documentation:

For applications created with Dynatrace version 1.238+, the RUM JavaScript reports some request errors using custom status codes 970–979 when the real HTTP status code can't be captured. Note that these custom status codes are not real HTTP status codes; they just mean that the RUM JavaScript detected an error fired by the framework you use.

Customer wan't change his "very good code" because it's insanely expensive.

I have already checked behavior with extended log of JS agent loaded on page. Already checked all information from support archive and HAR sessions of problematic behavior.

Also - I have tried to exclude this page with injection rule. It also didn't help

Regards,

Alex

[Julius_Loman]

So the issue is the web application does not work properly when RUM JS code is injected? 
Or do they complain about seeing the 97x errors in the waterfall?

[Romanenkov_Al3x]

Yes, the issue is that the web application does not work properly when RUM JS code is injected.

I see 97x errors in problematic sessions. 

[Julius_Loman]

Then you should open support ticket for that. Most likely the application is written in a way that including the RUM breaks it. The 97x errors are just the effect of the application itself not working.

I'd not recommend turning off the capture of 97x errors.

[Romanenkov_Al3x]

Thanks. I will.

[STEELERSROCK]

What was the outcome of the support ticket?  I'm seeing the same issue.

Thanks!