Willem Jiang <willem.ji...@gmail.com> 于2019年9月3日周二 上午4:23写道：
> Hi, > > As ServiceComb Pack use the GlobalTransactionId to trace the > distributed transactions, it's make sense that let the ServiceComb > Pack and Skywalking share the same Id for tracing. > In this way, we can bring the APM feature into Distribution > Transaction managemet world. > > Current ServiceComb has Interface IdGenerator[1], which is used for > the generate the GlobalTransactionId in OmegaContext[2]. I think if we > can reuse the transaction implementation with the Skywalking agent to > generate the GlobalTransactionId. In this way we can search the trace > information and transactions with same correlation ID. > For local, SkyWalking uses SegmentID if the request in one thread. I am not sure is it fitting your case? The across thread case will be covered by Ref(linking two segmentId, like RPC). > > The missing part is LocalTransactionId, we need to figure a way to > bring the LocalTransactionId with the trace information. > > BTW, ServiceComb Pack is using ES to store the Transaction related > event[3]. I think we can provide a service to bridge the Trace > information that Skywalking collects with ServiceComb Pack Transaction > events information. > SkyWalking has provided the GraphQL query API to get any trace by trace id. Sheng Wu 吴晟 Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin Twitter, wusheng1108 > > Any thoughts? > > [1] > https://github.com/apache/servicecomb-pack/blob/master/omega/omega-context/src/main/java/org/apache/servicecomb/pack/omega/context/IdGenerator.java > [2] > https://github.com/apache/servicecomb-pack/blob/master/omega/omega-context/src/main/java/org/apache/servicecomb/pack/omega/context/OmegaContext.java > [3]https://github.com/apache/servicecomb-pack/tree/master/alpha/alpha-fsm > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem >
