make it possible to associate a ConnectionTracer with a Session #3146
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.
Fixes #3145.
This PR implements a combination of the options discussed on the issue:
logging.Tracer.NewConnectionTracer
now takes acontext.Context
, which has values associated with it.Session.Context
have a context with aSessionTracingKey
value (which is a uint64).NewConnectionTracer
is derived from the context passed toDial
. This allows us (for example) to associate the peer ID we were dialing even if the handshake fails (and noSession
is returned).@mvdan, how does this look to you?