RUMM-2608: Use event write context for Traces#1106
Merged
0xnm merged 1 commit intoOct 27, 2022
Merged
Conversation
0xnm
force-pushed
the
nogorodnikov/rumm-2607/use-eventwritecontext-for-logs
branch
from
October 27, 2022 11:44
cd86390 to
169cbec
Compare
Base automatically changed from
nogorodnikov/rumm-2607/use-eventwritecontext-for-logs
to
feature/sdkv2
October 27, 2022 12:36
xgouchet
approved these changes
Oct 27, 2022
0xnm
force-pushed
the
nogorodnikov/rumm-2608/use-event-write-context-for-traces
branch
from
October 27, 2022 12:43
e8b3371 to
9720e9c
Compare
0xnm
deleted the
nogorodnikov/rumm-2608/use-event-write-context-for-traces
branch
October 27, 2022 13:04
This was referenced Oct 31, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR brings the usage of event write context (which can be retrieved by calling
withWriteContext) for traces.It is done by changing the
TraceWriterso that it requests event write context for the collection ofDDSpanto write.EWC will be requests only once, so that DD context is the same for all the spans to be written.
Also introduced
ContextAwareMapperandContextAwareSerializer, because both mapping (from legacyDDSpantoSpanEventand serialization) requireDatadogContextaccess, and options like to create them each time inside EWC or usePair<DatadogContext, T>as argument seemed less reasonable to me.Review checklist (to be filled by reviewers)