-
Notifications
You must be signed in to change notification settings - Fork 462
ddtrace/tracer: changed default tracecontext propagation order #2072
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
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.
Looks good! Just double checking, does the order matter in the extractor?
BenchmarksBenchmark execution time: 2023-07-07 14:39:03 Comparing candidate commit 6ed4f12 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 27 metrics, 0 unstable metrics. |
Summarizing what was discussed offline
|
Will close the PR for now |
What does this PR do?
Following the issues in serverless context propagation, this PR updates the propagation order to
datadog
Motivation
Describe how to test/QA your changes
Reviewer's Checklist