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
Long term plans for current OpenTracing implementation? #249
Comments
Would you be open to a PR to introduce a |
all prs are welcome |
@casualjim I've started work on this in #254 |
@casualjim I think the pull request is pretty much ready for review now. There are a few additional test cases I'd like to add but the bulk of the implementation is ready whenever you have the time. |
Now that #254 has been merged it feels like this can be closed. |
Whilst looking at options for tracing egress traffic within services I noticed go-openapi currently supports OpenTracing via its
WithOpenTracing
extension. Given OpenTracing has since been archived (and the SDK deprecated) and become part of OpenTelemetry I'm interested to know the future plans for this API within go-openapi and whether you'll eventually look at migrating to OpenTelemetry?The text was updated successfully, but these errors were encountered: