You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/09/23 15:11:10 UTC

[GitHub] [skywalking] wu-sheng commented on issue #2653: Improve Zipkin<->SkyWalking integration

wu-sheng commented on issue #2653: Improve Zipkin<->SkyWalking integration
URL: https://github.com/apache/skywalking/issues/2653#issuecomment-534143633
 
 
   > Will this solution solve the problem in certain degree?
   
   I wouldn't recommend to do that. Because, if you dig a little deeper, you will find there is another issue, which is the Zipkin span could include optional tags. Meaning, you can't guarantee the segment built successfully.
   
   I think I have proposed the design, you could build OAL Source(s) from Zipkin spans directly, about how to built that, I recommend Redis or Kafka(MQ) to find the client/server span match. You don't need the whole segment and trace.
   
   Then for trace details, using current SkyWalking ElasticSearch Zipkin storage.
   
   Look forward we could do this in this repo.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services