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:53:14 UTC

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

wu-sheng edited a comment on issue #2653: Improve Zipkin<->SkyWalking integration
URL: https://github.com/apache/skywalking/issues/2653#issuecomment-503172020
 
 
   > 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 metrics data?
   
   I mean analysis metrics from traces, like we did from SkyWalking traces. We just don't have JVM.
   
   > 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?
   
   Same as above, I was talking about `analysis metrics from Zipkin trace`.
   
   > And I am trying to implement the SW agents for components of our framework . They remake many wheels like the Driver/rpc/webdispatcher etc. It looks like that to implement agents is the easier way to work out. The Skywalking agent SDK is really very good.
   
   In most cases, I think agent plugin should be much better, and have better performance.

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