Allow span 'kind' to be set (e.g. CLIENT|SERVER|CONSUMER|PRODUCER) #53
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.
The goal here is to be able to identify spans as either 'CLIENT', 'SERVER', 'CONSUMER', or 'PRODUCER' - such that their relationships on a service graph can be mapped, like this:
Since the package doesn't have a Guzzle outbound HTTP request, you only see the 'SERVER' implementation of this new "kind" that can be set on the raw span.