-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ref: Read propagation context off of scope and isolation scope when propagating and applying trace context #10297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
size-limit report 📦
|
4e4f46e
to
36d4cfe
Compare
const sentryBaggageHeader = dynamicSamplingContextToSentryBaggageHeader(dynamicSamplingContext); | ||
setHeadersOnRequest(request, sentryTrace, sentryBaggageHeader); | ||
} | ||
const { traceId, spanId, sampled, dsc } = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
l: It feels like maybe we could extract this into a util 🤔 as this appears to be the same as for http? (and maybe others)
@@ -2,10 +2,43 @@ import type { DynamicSamplingContext } from './envelope'; | |||
|
|||
export type TracePropagationTargets = (string | RegExp)[]; | |||
|
|||
/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great comments ❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work on that - it is always a bit hard to follow along everywhere and ensure the behavior is "expected" but this seems to me like a massive simplification & streamlining of all of that.
0f28ba7
to
3314892
Compare
tracingContextFromHeaders
.