[Bug]: HTTP Information Not Available In X Ray Headers

[5t33]

Which web client version did you detect this bug with?

v1.14.0

What environment (build systems, module system, and framework) did you detect this bug with?

TypeScript v4.7.4, node v19.7.0, React ^17.0.0

Is your web application a single page application (SPA) or multi page application (MPA)?

None

Please provide your web client configuration

      const config: AwsRumConfig = {
        allowCookies: true,
        enableXRay: true,
        guestRoleArn: awsRumGuestRoleArn,
        identityPoolId: awsRumIdentityPoolId,
        sessionSampleRate: sessionSampleRate,
        telemetries: [
          'errors', 
          [ "performance", {recordAllTypes: ['document', 'script', 'other']} ],
          [ 'http', {
            recordAllRequests: true,
            addXRayTraceIdHeader: true,
            urlsToExclude: [
              new RegExp('/audio-samples/.+'),
              new RegExp('https://dataplane.rum.us-west-2.amazonaws.com/.+')
            ]
          } ]],
        eventPluginsToLoad: []
      };

Please describe the bug/issue

Hi,

I'm seeing HTTP traces coming from my app in my X Ray console, however, they lack any headers that allow me to sort or filter them.

I have X Ray set up on the backend with this package: https://github.com/narando/nest-xray. For reference, this is how my X Ray console looks without the RUM X Ray segments:

As you can see, URLs and status codes are sortable & filterable. However, when I implement RUM, I get this:

Only trace IDs. And when you dig into the trace, you can see that the top level of the trace doesn't include the HTTP info:

It's somehow obscured by the parent "app monitor" trace.

Is this something in my set up?

[haotiantest]

Hey Steven, in the trace tables, they are showing segment infomations, but when RUM web client generate traces, we put http object in the sub-segment document, that's why it's not showing in the table but if you look at the raw segment data you will able to see it there. We will evluate to see if we can add http object into segment level as well.

[qhanam]

I agree with @5t33 -- I think this is worth fixing. The top-level trace segment is effectively the HTTP request, and so it should contain all the properties of the HTTP request.

As shown in the screenshot, the X-Ray console only shows the status/response time/http method/url of the root trace segment. Among other things, this makes it difficult to select a trace for debugging purposes.

[flochaz]

Inspecting the raw trace, it is linked to the fact that root segment is not in it. So the issue is probably due to the fact that the root segment that should come from RUM is not received by XRay or is getting in late.
I got a full trace properly built :

And then I guess the URL in traces :

Will continue to investigate why it randomly works ...

[flochaz]

On my side the issue was the way I was setting my regex for addXRayTraceIdHeader. Not sure what was wrong with new RegExp constructor but going straight for a regex like addXRayTraceIdHeader: [/api\.\w+\.example\.com/], worked