-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Integrate with SkyWalking distributed tracing framework #12486
Comments
Thanks for raising this, we do also have similar use case. I'm happy to sponsor. |
is any process for this work? @lizan We are about to do the same. But I don't know what the community's plans are. |
@wbpcode if you’re interested I think you can take this. I can help you on the review. |
@wbpcode I actually have an initial code for this. If you think it will be helpful for you to get started, I can share it with you. |
@dio Thank you very much. I can try it out. Because we desperately need this feature and are willing to share the end result. |
Here you are: https://github.com/envoyproxy/envoy/compare/master...dio:sky-tracer?expand=1. I think it compiles and I had a docker-compose setup to "manually" test it (two services, with envoys, oap-server, and UI), I'll clean up the test bed and share it with you. |
It will be great to have Skywalking integration with Envoy. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
It's over. May be we can close it. @zyfjeff |
@wbpcode Great work, I'll close it |
I am from Alibaba Cloud team. We provide cloud service for hosted Istio/Envoy as a mesh solution.
Some of our users are using Apache SkyWalking language agents in their services, now, they want to migrate to the Istio mesh solution.Apache SkyWalking has provided fully topology, metrics, and alarms solution in the service mesh scenario,
but we still want the Envoy could support tracing by following the SkyWalking data model, which is different from the Zipkin model.
The Context Propagation should follow this, Standard Header Item is enough for step one.
https://github.com/apache/skywalking/blob/master/docs/en/protocols/Skywalking-Cross-Process-Propagation-Headers-Protocol-v3.md
The spans should follow this,
https://github.com/apache/skywalking-data-collect-protocol/blob/master/language-agent/Tracing.proto#L28-L31
@lizan
The text was updated successfully, but these errors were encountered: