Set XMLHttpRequest Instrumentation to use traceparent meta tag on initial page load

[paychex-ssmithrand]

I have dynamically generated HTML being served from an instrumented Ruby On Rails controller. That controller initiates the root span and sets the meta tag on the generated HTML appropriately. On the client side, I have both DocumentLoadInstrumentation and XMLHttpRequest Instrumentation enabled.

Since DocumentLoadInstrumentation has built-in code to continue using the passed trace context via the traceparent meta tag, it correctly correlates its generated Spans. However, calls to APIs are being made as part of page initialization and XMLHttpRequest Instrumentation is not using the traceparent context, causing each call to have its own trace id. This behavior makes sense when API calls are being made after page load and the user is interacting with the app, but is it possible to flag that instrumentation to use the traceparent context on page load only?

Currently, our Collector is not exposed publicly, so just using DocumentLoadInstrumentation and exporting those Spans is not an option (for now). The API endpoints that get called are right back to other Ruby controllers, which means they will be collected and can be correlated on the backend.

Thoughts here?

[syonip]

Did you ever find how to make XMLHttpRequest use the same traceparent?