-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
use LinkedTo rather than ChildOf for PublicEndpoint #272
Conversation
@freeformz @freeformzSFDC @iredelmeier FYI, and thank you <3 |
opt = trace.ChildOf(sc) | ||
// If the endpoint is a public endpoint, it should start a new trace | ||
// and incoming remote sctx should be added as a link. | ||
opt = trace.LinkedTo(sc) | ||
} else { // not a private endpoint, so assume child relationship | ||
opt = trace.ChildOf(sc) |
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.
On this note, aren't we removing ChildOf
? I'm on the fence about this, because we still haven't fully clarified SpanKind
. open-telemetry/opentelemetry-specification#337
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.
In either case we need a way to set the parent relationship, regardless of whether it's precisely specified according to SpanKind
or more generic.
I am fine with punting this until we more fully remove ChildOf and just updating in place when we do so.
Exigency: need this code in the repo for OTel workshop tomorrow to behave correctly. It has a maintainer and approver stamp on it, so using governance powers to merge. |
This causes us to no longer emit missing root spans if we do not have the trace associated with the tracing headers we receive on public endpoints.