[OpenTracing bridge] Support setting span kind tag after the creation of span #3997
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.
Resolves #3953
A few middleware frameworks (e.g https://github.com/yarpc/yarpc-go/blob/600cb49cc6331d8d15f65c058615a7649447efa7/api/transport/propagation.go#L67) that our company is using still set the OT span kind tag after a span is created.
Missing the span kind tags will impact a few functionalities in Jaeger (one of the OpenTracing implementations) that reply on the span kind tags.
Setting span kind tag in the bridge after a span is created cannot really set the SpanKind of OTel span, but adds the attribute instead which still helps in our case a lot.