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/06/18 14:12:56 UTC

[GitHub] [skywalking] Duncan-tree-zhou edited a comment on issue #2653: Improve Zipkin<->SkyWalking integration

Duncan-tree-zhou edited a comment on issue #2653: Improve Zipkin<->SkyWalking integration
URL: https://github.com/apache/skywalking/issues/2653#issuecomment-503152524
 
 
   > The most important enhancement are analysis metrics from zipkin span. This means, match zipkin client-server span and generated SkyWalking scopes(Service, ServiceRelation, etc.), like SourceBuilder used by MultiScopesSpanListener.
   
   for my understanding, zipkin reporter did not collect metrics information(since zipkin did not support to collect metrics data).  if you have no hand you can't make a fist. so i think maybe you can recomend users to use a metrics agent to collection the matrix data?
   
   > I think mostly is in OAP cluster mode. Zipkin spans of a trace could be sent to the different instances in an uncertain time, so, we need to make client/server match perfectly. Such as using Redis Cluster to be central cache?(Maybe only)
   
   I am not understanding that if SW had save the zipkin spans in db(like es). why a central cache is needed? why the storage can't be the data central?

----------------------------------------------------------------
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