-
Notifications
You must be signed in to change notification settings - Fork 443
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
Passing parent context to SpanProcessor::OnStart() #552
Conversation
Codecov Report
@@ Coverage Diff @@
## main #552 +/- ##
==========================================
+ Coverage 94.31% 94.33% +0.02%
==========================================
Files 198 198
Lines 8806 8807 +1
==========================================
+ Hits 8305 8308 +3
+ Misses 501 499 -2
|
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.
Thanks for getting us more closer to spec conformance.
const opentelemetry::trace::SpanContext &parent_context = | ||
opentelemetry::trace::SpanContext::GetInvalid()) noexcept override; |
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.
Any reason for having a default value here? According to the spec this parameter is required, so I think we shouldn't make it easy to omit it.
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.
Yes right, it should be required parameter. I have modified the function prototype accordingly.
…metry-cpp into span-processor-parent-id
as per spec https://github.com/open-telemetry/opentelemetry-specification/blob/7e0c10260178b947777cf9c11d7f7ac4d4700725/specification/trace/sdk.md#onstart
SpanProcessor.onStart()
should have a parent Context as parameter.fixes: #550