-
Notifications
You must be signed in to change notification settings - Fork 100
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
Open tracing support? #11
Comments
Hi, please see a response here: https://forums.aws.amazon.com/thread.jspa?threadID=272498&tstart=0 |
@haotianw465 Thanks mate. I have added more details on the forum question opened by me. |
@haotianw465 I've actually started building an xray-opentracing bridge internally for my current company, and I have a couple of questions:
Thanks |
Hi Ashley, We're 100% supportive of any and all open-source projects! In fact, we have a few collaborations going on at the moment. If you would want any input from our end we are happy to help. You can refer to our collaboration with Cookpad here: https://github.com/cookpad/aws-xray If you'd like and are open to it, we would be happy to host it under our AWS Labs project. |
Hey guys. |
Hi Dmytro :)
Actually, it looks like they got around to adding X-Ray support to the SDK v2 in the last few weeks. I haven't tried it yet, but if you upgrade to version 2.2.1 of the Java SDK you should be set: https://github.com/aws/aws-xray-sdk-java/blob/master/CHANGELOG.md
Actually, it is - although there are few inconsistencies in the API that you have to work around. As I mentioned above, we have a basic working version at my company except (a) it's currently written in Scala, so would need to be reworked in Java and (b) I haven't had time to open source it yet - but hopefully soon and will report back on this thread when it's done :) Hope that helps, Ashley EDIT: I've created an (as-yet, empty) repo for this work, hopefully should have something in the next week or two: https://github.com/ashleymercer/opentracing-java-aws-xray |
|
Okay, after some back-and-forth with my company we've agreed to host this under a company organization on github. The first version of the code is here: https://github.com/skylight-ipv/opentracing-java-aws-xray @dmytro-bekuzarov if you get a chance, would you be able to try it out? I'm still figuring out signing and deployment to maven repos, so you'll need to build from scratch with maven 3.6.0 or higher. @awssandra @haotianw465 would you be able to give the code an initial once-over? I think my broad approach is correct (just wrap the underlying |
Update: this has now moved to live under the opentracing-contrib project: |
Just to keep this issue up to date: there is a move to unite two previous projects (OpenTracing, mentioned here, and a similar project called Open Census). The combined, unified API will be called OpenTelemetry and the goal is to have the spec nailed down by the end of this year, I believe. @tosheer @haotianw465 I'd like to propose updating this issue to "Native OpenTelemetry support". |
@ashleymercer We are exploring solutions to ensure cross standard compatibility. Just out of curiosity, will you be contributing to the OpenTelemetry project emitters/bridges to work with X-Ray ? |
@ss2305 that would be awesome! Are you happy / able to update this existing issue, or is it worth creating a new one? Presumably this would be a new version (v3?) of the X-Ray libraries? I'm not currently involved in OpenTelemetry directly, although I am on various mailing lists so trying to keep up with what's going on! If there are specific projects / repos you think I could help with, please point me in the right direction and I'll try to help where I can. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The X-Ray SDK has been implemented with the OpenTelemetry API standard in a new repo. It will continue to be updated as the OpenTelemetry team updates their API specification. Note that both the API specification, and with it our implementation, are in early, experimental stages. Please raise any issues with our integration on that repository. Thank you! |
Are you guys planing to adhere to open tracing specification?
The text was updated successfully, but these errors were encountered: