X-Ray incorrectly reports status for requests ending in server faults as 200 OK

[seekingtheoptimal]

Similar to this one, but no AWS Lambda involved, the .net core app is running in EBS environment.

This is a critical bug for ages now.
A reproducible test case or series of steps:

• have any request in a .net core web api end with some internal error 5xx, and in X-Ray seems like all is fine with 200 Ok responses.

AWSXrayRecorder SDK version 2.10.1
.net version 5.0

[jj22ee]

Hi @seekingtheoptimal,
Can you try upgrading the SDK to the latest version (2.13.0) and see if this fixes the issue?

Otherwise, can you provide the raw trace data of this problematic segment? It may help us pinpoint the location of this possible instrumentation issue.

[jj22ee]

@seekingtheoptimal can you show how you are instrumenting WebAPI-prod? Are you manually creating Segments and attaching the exception to the Segment, or are you using the app.UseXRay() middleware for server instrumentation?

If you are using app.UseXRay(), can you confirm if this is used before all other middleware? Can you also make sure that you are correctly following the instructions (1) and (2) in the ASP.NET Core Framework (.NET Core) section of the README? They may be related to the status code issue and I want to make sure to eliminate all possible sources of error.

• The status code showing 200 occurred in the past when using .Net Core 2.0 due to a known limitation of the ExceptionHandler middleware. As you are using .net Version 5.0, this issue could be related.