-
Notifications
You must be signed in to change notification settings - Fork 39
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
dapper&opentracing #22
Comments
opentracing does not define how to represent remote operations, so what you
are mentioning is how some choose to do it (or perhaps example code), right?
zipkin predates OT by a while, and its data model was written for RPCs
sharing span for client and server. That said, you'll notice
zipkin-go-opentracing has a flag on how to handle remote spans (ex shared
span or not).
Regardless, there's still work needed to support a single-host model, and
the primary driver for this work is OT which while doesn't explicitly
require single-host spans, in practice, many assume it.
openzipkin/zipkin#1480
|
thanks for your answer, in brave-opentracing, |
actually, you'd want to use |
oh i see, thanks so much |
I have a question, zipkin is based on dapper, and cs,cr,ss,sr have the same spanid. But in opentracing, cs,cr and ss,sr do not have the same span id ,and they have a child of relationship. Is that may have some influence?
Looking forward for your answer!
The text was updated successfully, but these errors were encountered: