adhere to timestamp best practices for RPC mode server side spans #34
Conversation
This file contains 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
richardmarshall
pushed a commit
to richardmarshall/zipkin-go-opentracing
that referenced
this pull request
Dec 13, 2016
…_header Adding back william's header previously lost to the branches of time.
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.
In the past the tracer would always record and report timestamp and duration for each span.
To adhere to best practices the tracer will not report timestamp and duration in
clientServerSameSpanmode for server side spans that have an existing client side counterpart.See: openzipkin/openzipkin.github.io#49