-
Notifications
You must be signed in to change notification settings - Fork 140
RUM-9747 Strongly-typed Trace Additional Context #2293
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
RUM-9747 Strongly-typed Trace Additional Context #2293
Conversation
Datadog ReportBranch report: ✅ 0 Failed, 708 Passed, 3186 Skipped, 2m 13.95s Total duration (2m 23.1s time saved) |
9a71de0
to
eb6381b
Compare
4d4de31
to
e53d667
Compare
e53d667
to
8b6640f
Compare
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!
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.
Neat! 🎯
8b6640f
to
71b9fcf
Compare
71b9fcf
to
48a1427
Compare
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What and why?
Following: #2289
FeatureBaggage
comes with perf implications, we are replacing loosely-typed baggages in core context by strongly-typed additional context.How?
Replace Trace baggage by
SpanCoreContext
as additional context.Bonus
Also fix a left-over from #2277 and replace the Trace baggage message to logs by a
.payload(TraceLogMessage)
.Review checklist
make api-surface
)