Hi there! We're using Sentry as part of our observability toolkit, and part of what they offer is distributed tracing. Soon, we'll integrate with their browser tracing feature, which will attach a trace ID as

Sentry-Trace

on every single XHR request (including ones to Medplum). We saw that there are docs showing that Medplum supports an

X-Trace-Id

header. Is it possible for Medplum to check for a

Sentry-Trace

header and use that as the trace ID? That would give Medplum support for Sentry's distributed tracing out-of-the-box, which would be pretty rad. Otherwise, we'll have to do some extra work to grab the sentry trace ID and add that to medplum requests as an

X-Trace-Id

header. Definitely doable, but a bit of a pain.

It seems that even if

X-Trace-Id

were set to the

Sentry-Trace

value by the client, the Medplum server would currently ignore it because it is not a UUID. https://github.com/medplum/medplum/blob/f86debc144a6bb73169bec8b0bf12bebaadeb6b0/packages/server/src/context.ts#L106 https://github.com/getsentry/sentry-javascript/blob/6dfddc2dfc4b74cbb70dc325b4af165e25904ed4/packages/utils/src/tracing.ts#L117-L130 I've opened this PR to have the Medplum server directly support the

Sentry-Trace

header https://github.com/medplum/medplum/pull/3877

Hi @node @yaaaaale - We really appreciate the contribution, but unfortunately, we don't plan to support vendor-specific logic in our servers.

Agreed that properly aligning with the

traceparent

spec unblocks distributed tracing for at least Sentry, though it would require additional client configuration.

yeah, it seems like the sentry header is just the traceparent format, minus the flags and preceding

00

. There might be a middle ground here where we can consider those optional when we parse the

traceparent

header