-
Notifications
You must be signed in to change notification settings - Fork 435
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
Fix: Support custom propagators in startup log #2925
Conversation
BenchmarksBenchmark execution time: 2024-10-18 15:15:44 Comparing candidate commit e0e305c in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 58 metrics, 0 unstable metrics. scenario:BenchmarkInjectW3C-24
|
ddtrace/tracer/log_test.go
Outdated
var stop func() | ||
if customProp != nil { | ||
tracer, _, _, stop = startTestTracer(t, WithLogger(tp), WithPropagator(customProp)) | ||
// tracer = newTracer(WithLogger(tp), WithPropagator(customProp)) |
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.
nit: is this comment relevant?
The same for its sibling below.
What does this PR do?
Modifies the logic within the startup log for determining values for propagation injectors and extractors.
Fixes #2923
Motivation
The previous logic expected to cast the current propagator to a *chainedPropagator, but that's not always viable, especially in the case that a custom propagator has been registered on the tracer via the WithPropagator StartOption.
Reviewer's Checklist
Unsure? Have a question? Request a review!