Re: Fw: Request the Permission using Apache ServiceCom(incubating) namein our Meetup
Hi Sally
Apache SkyWalking (incubating) project will join the meeting too. We will
follow the rule.
--
Sheng Wu
Apache SkyWalking creator and PPMC member
-- Original --
From: "Sally Khudairi"<s...@apache.org>;
Date: Wed, Mar 14, 2018 11:13 AM
To:
"willem.jiang"<willem.ji...@gmail.com>;"dev"<dev@servicecomb.apache.org>;"ASF
ComDev"<d...@community.apache.org>;
Cc: "ASF Marketing & Publicity"<pr...@apache.org>;
Subject: Re: Fw: Request the Permission using Apache ServiceCom(incubating)
namein our Meetup
Hello Willem --thank you for your message.
There are no issues with your use of the podling name to help promote
your event and help build your community as long as the naming is along
the lines of "Apache ServiceComb (incubating) MeetUp". If you can
please confirm the name of your event, we'd appreciate it.
I am copying ASF Community Development ("ComDev") here for their
attention and follow-up as needed.
Welcome to the Apache family; do let me know if there's anything else we
can help with.
Kind regards,
Sally
- - -
Vice President Marketing & Publicity
The Apache Software Foundation
Tel +1 617 921 8656
Skype sallykhudairi
- Forwarded Message - **From:** Willem Jiang
<willem.ji...@gmail.com> **To:** pr...@apache.org **Cc:**
dev@servicecomb.apache.org **Sent:** Tuesday, March 13, 2018 10:45 PM
**Subject:** Request the Permission using Apache ServiceCom(incubating)
name in our Meetup>
> Hi ASF Marketing & Publicity,
>
> We will hold a meetup in Beijing, China at March 31, 2018, by using
> Apache ServiceComb(incubating) as part of the event name to build up
> the Apache ServiceComb community.>
> I want through the document of small-events tips[1], which said we
> need approve from the PMC. As ServiceComb is in the Apache incubator,
> so we only has PPMC for project management, and there is no detail
> guide for holding the event with project name in the incubator guide.>
> So I just ask for permission of using the name of Apache
> ServiceComb(incubating) in this meetup.>
> [1]http://community.apache.org/events/small-events.html
>
> Thanks,
>
> Willem Jiang
>
>
Re: Fw: Fw: Request the Permission using Apache ServiceCom(incubating)namein our Meetup
Sally
Thanks, and changed.
--
Sheng Wu
Apache SkyWalking original creator and PPMC member
-- Original --
From: "Sally Khudairi"<s...@apache.org>;
Date: Wed, Mar 14, 2018 11:35 AM
To: " Sheng Wu"<wu.sh...@foxmail.com>;
Cc: "willem.jiang"<willem.ji...@gmail.com>; "dev"<dev@servicecomb.apache.org>;
"ASF ComDev"<d...@community.apache.org>; "ASF Marketing &
Publicity"<pr...@apache.org>;
Subject: Re: Fw: Fw: Request the Permission using Apache
ServiceCom(incubating)namein our Meetup
Thank you for notifying us, Sheng.
As with Apache ServiceComb, please be sure to send us the Apache
SkyWalking naming/promotions when available.
Also, I'm not sure if your Incubator mentor has mentioned it to you, but
creators/inventors of projects that are now at the ASF may be referred
to as "original creator/*"; your signature below should read "Original
creator of Apache SkyWalking" or "Apache SkyWalking original creator".
The ASF is about highlighting projects and their communities :-)
Kind regards,
Sally
- - -
Vice President Marketing & Publicity
The Apache Software Foundation
Tel +1 617 921 8656
Skype sallykhudairi
- Forwarded Message - **From:** Sheng Wu
<wu.sh...@foxmail.com> **To:** willem.jiang <willem.ji...@gmail.com>;
dev <dev@servicecomb.apache.org>; dev <d...@community.apache.org> **Cc:**
press <pr...@apache.org> **Sent:** Tuesday, March 13, 2018 11:16 PM
**Subject:** Re: Fw: Request the Permission using Apache
ServiceCom(incubating) namein our Meetup>
> Hi Sally
>
> Apache SkyWalking (incubating) project will join the meeting too. We
> will follow the rule.>
>
> --
> *Sheng Wu*
> Apache SkyWalking creator and PPMC member
>
>
>
> -- Original --
> *From: * "Sally Khudairi"<s...@apache.org>;
> *Date: * Wed, Mar 14, 2018 11:13 AM
> *To: * "willem.jiang"<willem.ji...@gmail.com>;"dev"<dev@servicecomb.a-
> pache.org>;"ASF ComDev"<d...@community.apache.org>;> *Cc: * "ASF Marketing &
> Publicity"<pr...@apache.org>;
> *Subject: * Re: Fw: Request the Permission using Apache
> ServiceCom(incubating) namein our Meetup>
> Hello Willem --thank you for your message.
>
> There are no issues with your use of the podling name to help promote> your
> event and help build your community as long as the naming
> is along> the lines of "Apache ServiceComb (incubating) MeetUp". If you can
> please confirm the name of your event, we'd appreciate it.
> I am copying ASF Community Development ("ComDev") here for their
> attention and follow-up as needed.
> Welcome to the Apache family; do let me know if there's
> anything else we> can help with.
> Kind regards,
> Sally
>
> - - -
> Vice President Marketing & Publicity
> The Apache Software Foundation
>
> Tel +1 617 921 8656
> Skype sallykhudairi
>
>
> - Forwarded Message - **From:** Willem Jiang
> <willem.ji...@gmail.com> **To:** pr...@apache.org **Cc:**
> dev@servicecomb.apache.org **Sent:** Tuesday, March 13, 2018 10:45 PM>
> **Subject:** Request the Permission using Apache
> ServiceCom(incubating)> name in our Meetup>
> > Hi ASF Marketing & Publicity,
> >
> > We will hold a meetup in Beijing, China at March 31, 2018, by using> >
> > Apache ServiceComb(incubating) as part of the event name to build up> > the
> > Apache ServiceComb community.>
> > I want through the document of small-events tips[1], which said we
> > need approve from the PMC. As ServiceComb is in the Apache
> > incubator,> > so we only has PPMC for project management, and there is no
> > detail
> > guide for holding the event with project name in the incubator
> > guide.>> > So I just ask for permission of using the name of Apache
> > ServiceComb(incubating) in this meetup.>
> > [1]http://community.apache.org/events/small-events.html
> >
> > Thanks,
> >
> > Willem Jiang
> >
> >
>
>
>
Re: Apache project meetup in ShangHai Oct 13th
I will be there to represent the skywalking. Welcome everyone to join us. Look forward to see you all. Sheng Wu Apache SkyWalking From Wu Sheng 's phone. -- Original -- From: Willem Jiang Date: Sat,Sep 29,2018 0:49 PM To: dev Subject: Re: Apache project meetup in ShangHai Oct 13th Hi Apache ServiceComb will hold a meetup in ShangHai Oct 13th, 1 PM to 4 PM, by inviting three Apache members (Roman Shaposhik??Justin Mclean?? Craig Russell, Willem Jiang) and the apache projects committer in China. We hold this meetup can help Apache projects to know each other in China. As there are lot of Apache project committers live around east China, we can leverage this opportunity to let Apache know better about the committers in China and give us some advice to build up health community. The discussion topic of meetup could be: How to be the TLP of ASF? How can we help ASF know better about China? How can we help more Chinese know better about ASF? If you are interested about this meetup, please drop an email to ningjiang AT apache.org with the information of your name, phone number and the project name before Oct 8th 12 PM. We will send you detail information of the meetup later. Please forward the mail to your friend who may interest about this event. Regards, Willem Jiang Twitter: willemjiang Weibo: willem 1
Re: Saga transaction performance test with Sharding-JDBC
Please set the name right. As a Chinese native, I noticed the name is even not the real Chinese name. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Craig Russell Date: Sat,Jan 5,2019 0:16 AM To: dev Cc: dev Subject: Re: Saga transaction performance test with Sharding-JDBC Hi tsubasa...@qq.com, Can you please update your "from:" address in your email client to include your English name? This will make it possible for non-Chinese-fluent people to know who the mail is from. Thanks, Craig > On Jan 4, 2019, at 12:24 AM, wrote: > > I am modifying the integration way of ShardingSphere and saga-actuator, > and the next performance test will be performed after the modification is > completed. > > > -- Original -- > From: "Willem Jiang"; > Date: Fri, Jan 4, 2019 04:10 PM > To: "dev"; > > Subject: Re: Saga transaction performance test with Sharding-JDBC > > > > Any updated about this performance test? > > Willem Jiang > > Twitter: willemjiang > Weibo: willem > > On Tue, Dec 25, 2018 at 4:31 PM wrote: >> >> XA use Atomikos as default. >> >> >> The test run with >> repo: >> https://github.com/cherrylzhao/sharding-sphere-example/tree/dev-performance >> module: sharding-jdbc-example --> spring-boot-nodep-example --> >> spring-boot-nodep-mybatis-example >> class: >> io.shardingsphere.example.spring.boot.mybatis.nodep.SpringBootStarterTransactionExample >> >> >> -- Original -- >> From: "Zheng Feng"; >> Date: Tue, Dec 25, 2018 04:05 PM >> To: "dev"; >> >> Subject: Re: Saga transaction performance test with Sharding-JDBC >> >> >> >> Thanks for sharing these performance tests and is it possible to share the >> source codes if you are happy to open these tests ? >> In term of the XA tests, I think the default transaction manager is >> Atomikos ? I'm interested with running with the Narayana [1] >> >> So it could be very useful to share the source codes with the community ! >> Thanks, >> >> Zheng Feng >> >> [1] https://github.com/zhfeng/narayana-sharding-sphere >> >> ??2018??12??25?? 10:51?? >> >>> Saga Tx is slower than No Tx. >>> TPS of saga is 1700 and No Tx is 2000 in test environment. >>> >>> >>> About the load and memory usage, we will record in next performance. >>> >>> >>> >>> >>> -- Original -- >>> From: "Zhang Yonglun"; >>> Date: Mon, Dec 24, 2018 08:56 PM >>> To: "dev"; >>> Cc: "dev"; >>> Subject: Re: Saga transaction performance test with Sharding-JDBC >>> >>> >>> >>> Impressive! >>> I am focused on the performance issue of ShardingSphere for a long time, >>> and have done a little saga work before. But I still can't understand why >>> saga Tx faster than No Tx. Is there something I missed? >>> >>> BTW, I noticed that second nice machine, and wonder what's the load and >>> memory usage on it when testing. >>> >>> >>> ??2018??12??24?? 6:28?? >>> >>>> Hi, everyone. >>>> >>>> >>>> The feature of saga transaction in ShardingSphere has been basically >>>> completed >>>> by integrating servicecomb-saga-actuator. >>>> Recently, we used Sharding-JDBC to test the performance of Saga >>>> transactions. >>>> >>>> >>>> There are results for two kinds of environments. >>>> >>>> >>>> First result comes from local environment which including 2 cores and 16G >>>> RAM >>>> The connection pool size, thread pool size of saga-actuator and thread >>>> pool size of Sharding-JDBC all are 50. >>>> >>>> >>>> result for local environment >>>> |Tx Type|Thread Number|Average response(ms)| TPS | >>>> | No Tx | 50 | 337| 140 | >>>> | saga | 50 | 395| 120 | >>>> | local | 50 | 323 |143| >>>> | xa | 50 | 301 |154| >>>> | No Tx |
Re: [saga-actuator]consider about adding StreamBasedSaga engine to integrate with shardingsphere
Feedback from our Seata and SkyWalking integration. We will provide plugins for there TC and TM. Also, Seata team has the plan to distribute their binary including SkyWalking binary tar in TC, for user convenience. Then users could use a single command in TC to open SkyWalking agent working with the globally distributed tracing system, and benefits from SkyWalking other monitoring/analysis capabilities. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Willem Jiang 于2019年5月1日周三 上午8:44写道： > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Apr 29, 2019 at 7:58 PM zhaojun wrote: > > > > Hi, Willem > > > > Saga actuator could not compatible with ShardingSphere currently, there > are 2 main problem exist. > > 1. If sql execute in saga transport instead of ShardingSphere, we can > not see the result of logic-sql even in one transaction, it is like this: > > update t_order set status=’start’ where usr_id=’tom’; > > select status from t_order where usr_id=’tom’; > —> we can’t query ’start’ record as actuator haven’t executed. > > Insert into t_order values(?,?,?) ; > > I think we can break the whole SQL interactions into smaller steps, > and let saga-actuator do the job one by one. > In this case, you can break the whole calling graph into several sub > calling graphs. > Any thought? > > > 2. If logic-sql execute in ShardingSphere, we cannot handle recovery > before submit graph result, as event log only wrote at saga engine. > > > > so we should integrate saga-transaction like omega send event log step > by step. > > It is better to make every instance do recovery Independently, instead > of providing another coordinator center service. > > I feel that embed saga should have following capability. > > 1).It can provide service in jar package independent > > 2).each embed saga only recovery their own transaction-data of this > instance. > >If one instance crashed, we can introduce external service to do > failover. > > > > so we consider about exending saga-acutator, if it can support submit > task step by step in one transaction, it is a good choice. > > of course, there have many things we should do. > > > > -- > > Zhao Jun > > Apache Sharding-Sphere & ServiceComb > > > > > On Apr 29, 2019, at 5:17 PM, Willem Jiang > wrote: > > > > > > First Saga actuator need to build up the calling grapha before sending > > > out the request. I don't think you can do the step by step SQL > > > invocation with Saga actuator. > > > If you want to call the SQL execution step by step , you may need to > > > switch to ServiceComb Pack project which has a coordinator to take > > > care of the distributed transaction. But that introduce another > > > endpoint(Alpha) to shardingsphere. > > > > > > From my understanding, Saga actuator is most efficient way to execute > > > the SQL across different data nodes. > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, Apr 26, 2019 at 6:41 PM zhaojun wrote: > > >> > > >> Hi, all > > >> > > >> currently, we have integrated with saga using graph based engine in > shardingsphere[1] > > >> it need us to collect all participated actual SQL, then submit to > saga actuator in commit/rollback phase. > > >> if application crashed before invoking saga actuator, undo log of > branch transaction SQL will not be saved, > > >> so recovery thread will not be executed correctly. > > >> > > >> it's better that encapsulating every actual SQL as a saga task in > shardingsphere side, > > >> then submit to saga actuator realtime instead of batch processing all > the SQLs at commit/rollback phase. > > >> this architecture will make the boundary more clear between > shardingsphre and saga, currently we have done some additional works for > integrating saga. > > >> > > >> any thought? > > >> > > >> [1]: > https://github.com/sharding-sphere/shardingsphere-spi-impl/tree/master/sharding-transaction-spi-impl/sharding-transaction-base-spi-impl/sharding-transaction-base-saga > < > https://github.com/sharding-sphere/shardingsphere-spi-impl/tree/master/sharding-transaction-spi-impl/sharding-transaction-base-spi-impl/sharding-transaction-base-saga > > > > >> > > >> > > >> > > >> -- > > >> Zhao Jun > > >> Apache Sharding-Sphere & ServiceComb > > >> > > >
Re: Integration of Skywalking agent with ServiceComb Pack.
Willem Jiang 于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 >
Re: Integration of Skywalking agent with ServiceComb Pack.
Willem Jiang 于2019年9月3日周二 下午6:25写道： > On Tue, Sep 3, 2019 at 10:52 PM Zhang Lei wrote: > > > > Hi Willem, > > > > I agree to integrate a transaction tracking service, I used Zipkin, but > I don't know much about Skywalking. > > > > I have some questions: > > > > 1. Skywalking agent just working on the Omega side? > Yep, but we can also let the agent do the instrumentation on the Alpha > side. > > 2. Use @Trace in the same location as @SagaStart and @Compensable, Or > Combined annotation? And use TraceContext.traceId() to generate globalTxId > or localTxId ? > This is the detail thing we need to think about. > I think you are just proposing a way to integrate the Zipkin, am I right? > @Trace is SkyWalking annotation, which SkyWalking agent could identify and instrument as a local span(Not RPC related) > > > 3. Will Omega users have conflicts if they already use Zipkin? > We need to do some end to end verification, currently I think it's > fine if we can find a way to generate a correlation id between tracing > system and pack, we don't need to deeply combine these two system > together, they can work separately. > SkyWalking doesn't conflict with Zipkin, but I don't recommend to use both at the same time, because it is pointless. > > > 4. About provides a service to bridge the Trace information that > Skywalking collects with ServiceComb Pack Transaction events information. > Do you mean that Alpha sends service chain information directly to > Skywalking via API? > It's more like a portal integration. We can still leverage the old API > provide by Skywalking and ServiceComb Pack. > In this way, we need to have a deeper discussion about what ServiceComb wants and requires. > > > > > > Lei Zhang > > > > > 在 2019年9月3日，下午7:22，Willem Jiang 写道： > > > > > > 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. > > > > > > 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. > > > > > > 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 > > >
Re: Integration of Skywalking agent with ServiceComb Pack.
We have a service comb RPC plugin, provided by you before. For pack and transaction, we need another plugin. There are a lot of plugins you could ref, and Seata plugin is WIP too, https://github.com/apache/skywalking/pulls. Wait for new protocol stable at Seata side. Sheng Wu 吴晟 Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin Twitter, wusheng1108 Zheng Feng 于2019年9月5日周四 上午7:28写道： > So we have to dev a new plugin for the servicecomb-pack or there is a > plugin we could leverage with ? > > Sheng Wu 于2019年9月5日周四 下午10:08写道： > > > Then SkyWalking has a toolkit lib[1], you could use > > `TraceContext.traceId()` in any place, if there is sw agent attached, and > > current context has been traced, you could have the trace id. > > > > [1] > > > > > https://github.com/apache/skywalking/blob/master/docs/en/setup/service-agent/java-agent/Application-toolkit-trace.md > > > > Sheng Wu 吴晟 > > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin > > Twitter, wusheng1108 > > > > > > Zheng Feng 于2019年9月5日周四 上午5:46写道： > > > > > Sheng Wu 于2019年9月4日周三 上午11:31写道： > > > > > > > Willem Jiang 于2019年9月3日周二 下午6:25写道： > > > > > > > > > On Tue, Sep 3, 2019 at 10:52 PM Zhang Lei > > > wrote: > > > > > > > > > > > > Hi Willem, > > > > > > > > > > > > I agree to integrate a transaction tracking service, I used > > Zipkin, > > > > but > > > > > I don't know much about Skywalking. > > > > > > > > > > > > I have some questions: > > > > > > > > > > > > 1. Skywalking agent just working on the Omega side? > > > > > Yep, but we can also let the agent do the instrumentation on the > > Alpha > > > > > side. > > > > > > > > > > > > > > 2. Use @Trace in the same location as @SagaStart and > @Compensable, > > Or > > > > > Combined annotation? And use TraceContext.traceId() to generate > > > > globalTxId > > > > > or localTxId ? > > > > > This is the detail thing we need to think about. > > > > > I think you are just proposing a way to integrate the Zipkin, am I > > > right? > > > > > > > > > > > > > @Trace is SkyWalking annotation, which SkyWalking agent could > identify > > > and > > > > instrument as a local span(Not RPC related) > > > > > > > > > > > > > > > > > > > 3. Will Omega users have conflicts if they already use Zipkin? > > > > > We need to do some end to end verification, currently I think it's > > > > > fine if we can find a way to generate a correlation id between > > tracing > > > > > system and pack, we don't need to deeply combine these two system > > > > > together, they can work separately. > > > > > > > > > > > > > SkyWalking doesn't conflict with Zipkin, but I don't recommend to use > > > both > > > > at the same time, because it is pointless. > > > > > > > > > > > > > > > > > > > 4. About provides a service to bridge the Trace information that > > > > > Skywalking collects with ServiceComb Pack Transaction events > > > information. > > > > > Do you mean that Alpha sends service chain information directly to > > > > > Skywalking via API? > > > > > It's more like a portal integration. We can still leverage the old > > API > > > > > provide by Skywalking and ServiceComb Pack. > > > > > > > > > > > > > In this way, we need to have a deeper discussion about what > ServiceComb > > > > wants and requires. > > > > > > > Basically, I think we need to track the saga transaction status by the > > > global id. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Lei Zhang > > > > > > > > > > > > > 在 2019年9月3日，下午7:22，Willem Jiang 写道： > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > As ServiceComb Pack use the GlobalTransactionId to trace the > > > > > > > distributed transactions, it's make sense that let the > > ServiceComb > > > > &
Re: Integration of Skywalking agent with ServiceComb Pack.
Then SkyWalking has a toolkit lib[1], you could use `TraceContext.traceId()` in any place, if there is sw agent attached, and current context has been traced, you could have the trace id. [1] https://github.com/apache/skywalking/blob/master/docs/en/setup/service-agent/java-agent/Application-toolkit-trace.md Sheng Wu 吴晟 Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin Twitter, wusheng1108 Zheng Feng 于2019年9月5日周四 上午5:46写道： > Sheng Wu 于2019年9月4日周三 上午11:31写道： > > > Willem Jiang 于2019年9月3日周二 下午6:25写道： > > > > > On Tue, Sep 3, 2019 at 10:52 PM Zhang Lei > wrote: > > > > > > > > Hi Willem, > > > > > > > > I agree to integrate a transaction tracking service, I used Zipkin, > > but > > > I don't know much about Skywalking. > > > > > > > > I have some questions: > > > > > > > > 1. Skywalking agent just working on the Omega side? > > > Yep, but we can also let the agent do the instrumentation on the Alpha > > > side. > > > > > > > > 2. Use @Trace in the same location as @SagaStart and @Compensable, Or > > > Combined annotation? And use TraceContext.traceId() to generate > > globalTxId > > > or localTxId ? > > > This is the detail thing we need to think about. > > > I think you are just proposing a way to integrate the Zipkin, am I > right? > > > > > > > @Trace is SkyWalking annotation, which SkyWalking agent could identify > and > > instrument as a local span(Not RPC related) > > > > > > > > > > > 3. Will Omega users have conflicts if they already use Zipkin? > > > We need to do some end to end verification, currently I think it's > > > fine if we can find a way to generate a correlation id between tracing > > > system and pack, we don't need to deeply combine these two system > > > together, they can work separately. > > > > > > > SkyWalking doesn't conflict with Zipkin, but I don't recommend to use > both > > at the same time, because it is pointless. > > > > > > > > > > > 4. About provides a service to bridge the Trace information that > > > Skywalking collects with ServiceComb Pack Transaction events > information. > > > Do you mean that Alpha sends service chain information directly to > > > Skywalking via API? > > > It's more like a portal integration. We can still leverage the old API > > > provide by Skywalking and ServiceComb Pack. > > > > > > > In this way, we need to have a deeper discussion about what ServiceComb > > wants and requires. > > > Basically, I think we need to track the saga transaction status by the > global id. > > > > > > > > > > > > > > > > > > > Lei Zhang > > > > > > > > > 在 2019年9月3日，下午7:22，Willem Jiang 写道： > > > > > > > > > > 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. > > > > > > > > > > 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. > > > > > > > > > > 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 > > > > > > > > > >
Re: Apache project meetup in ShangHai Sep 21st
Enjoy the meetup. It will be a great chance to meet senior Apache members/board, learning the Apache Way. I wouldn't join as my schedule has been too crazy already. If any of you will be Alibaba APSARA(云溪大会) next week, I will be there. :) Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 Willem Jiang 于2019年9月17日周二 下午4:16写道： > The time is around 1:30 PM to 4:00 PM, now it's about 20 people will join > us. > We are just trying to find some place to hold this event. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Sep 17, 2019 at 6:14 AM Liu Ted wrote: > > > > Hi Willem, What's the current status if the captioned meeting in > Shanghai on Seot. 21st? Has the venue and time been decided yet? > > > > Best regards, > > > > Ted Liu, > > ASF Member, Sponsor Ambassador, Incubator PMC Member > > > > > > 2019 年 8 月 21 日周三 10:55，Willem Jiang 写道： Hi, > > > > We would like to hold a meetup in ShangHai Sep 21st by inviting some > > Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some > > apache projects committers in China like we did last year. > > > > We hold this meetup can help Apache projects to know each other in > > China. As there are lot of Apache project committers are based in east > > China, we can leverage this opportunity to let Apache know better > > about the committers in China and give us some advice to build up > > health community. > > > > The discussion topic of meetup could be: > > How to be the TLP of ASF? > > How can we help ASF know better about China? > > How can we help more Chinese know better about ASF? > > > > If you are interested about this meetup, please drop an email to > > ningjiang AT apache.org with the information of your name, phone > > number and the project name before Sep 18th 12 PM. We will send you > > detail information of the meetup later. > > > > Please forward the mail to your friend who may be interested about this > event. > > > > Willem > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > > For additional commands, e-mail: dev-h...@echarts.apache.org > > >
Re: [PROPOSAL] Mesher supports skywalking
Any update? This seems going to dark. Sheng. Sheng Wu 于2019年10月14日 周一下午12:38写道： > Interesting proposal. > > Could you explain a little more about the topology? And what do you expect > after the integration? > > Sheng > > Willem Jiang 于2019年10月14日 周一上午10:06写道： > >> I think we can get some feedback from the skywalking community, so I just >> forward the mail to dev@skywalking >> BTW, you find the topology map here[1] >> [1] >> >> https://issues.apache.org/jira/secure/attachment/12982640/12982640_image-2019-10-10-15-05-02-666.png >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> >> On Fri, Oct 11, 2019 at 10:45 AM 陈硕 <814464...@qq.com> wrote: >> >> > Hello, everyone >> >Skywalking is a very popular application performance management >> > software. We can enhance the performance management capability of >> mesher by >> > accessing skywalking. >> >Now I accessed skywalking using the manual-SDK go2sky( >> > https://github.com/tetratelabs/go2sky) recommended by the official >> > website . Unlike java-sdk , the SDK of golang need manually create and >> end >> > span to send messages to the skywalking server. Now I'm ready to adjust >> the >> > code. I want to put the code in the proxy/pkg directory. Create an APM >> > management directory and use go2sky as a client. >> > >> > Skywalking draws Mehser's topology as follows： >> > >> > Looking forward to your suggestions. >> > >> > -- >> > 陈硕 >> > 邮箱：814464...@qq.com >> > >> > >> > -- > Sheng Wu > SkyWalking, Shardingsphere and Zipkin > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
Re: [PROPOSAL] Mesher supports skywalking
I have followed up that ticket, let's continue the discussion there. FYI +高洪涛@skywalking I think you should be there too. https://issues.apache.org/jira/projects/SCB/issues/SCB-1497 Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 陈硕 <814464...@qq.com> 于2019年10月17日周四 下午3:56写道： > Hello， > Thanks for your attention. > Because the mail does not support pictures. I submitted the topology > picture to JIRA > https://issues.apache.org/jira/projects/SCB/issues/SCB-1497 > I has created a PR to apache/servicecomb-mesher and is waiting for review > now. > > Looking forward to your suggestion. > > > > 陈硕 > 邮箱：814464...@qq.com > > > > > > > > > > -- 原始邮件 -- > 发件人: "Bin Ma"; > 发送时间: 2019年10月17日(星期四) 晚上8:08 > 收件人: "dev"; > 抄送: "dev"; > 主题: Re: [PROPOSAL] Mesher supports skywalking > > > > hi @陈硕 > I think you can open a issue in Apache ServiceComb JIRA > to save your topology attachment , and feedback the link in the mailing > list . > > Best Wishes & Regards > --- > Mabin > > > > Sheng Wu 于2019年10月17日周四 下午2:46写道： > > > Any update? This seems going to dark. > > > > Sheng. > > > > Sheng Wu 于2019年10月14日 周一下午12:38写道： > > > > > Interesting proposal. > > > > > > Could you explain a little more about the topology? And what do you > > expect > > > after the integration? > > > > > > Sheng > > > > > > Willem Jiang 于2019年10月14日 周一上午10:06写道： > > > > > >> I think we can get some feedback from the skywalking community, so I > > just > > >> forward the mail to dev@skywalking > > >> BTW, you find the topology map here[1] > > >> [1] > > >> > > >> > > > https://issues.apache.org/jira/secure/attachment/12982640/12982640_image-2019-10-10-15-05-02-666.png > > >> > > >> Willem Jiang > > >> > > >> Twitter: willemjiang > > >> Weibo: 姜宁willem > > >> > > >> > > >> On Fri, Oct 11, 2019 at 10:45 AM 陈硕 <814464...@qq.com> wrote: > > >> > > >> > Hello, everyone > > >> >Skywalking is a very popular application performance management > > >> > software. We can enhance the performance management capability of > > >> mesher by > > >> > accessing skywalking. > > >> >Now I accessed skywalking using the manual-SDK go2sky( > > >> > https://github.com/tetratelabs/go2sky) recommended by the official > > >> > website . Unlike java-sdk , the SDK of golang need manually create > and > > >> end > > >> > span to send messages to the skywalking server. Now I'm ready to > > adjust > > >> the > > >> > code. I want to put the code in the proxy/pkg directory. Create an > APM > > >> > management directory and use go2sky as a client. > > >> > > > >> > Skywalking draws Mehser's topology as follows： > > >> > > > >> > Looking forward to your suggestions. > > >> > > > >> > -- > > >> > 陈硕 > > >> > 邮箱：814464...@qq.com > > >> > > > >> > > > >> > > > -- > > > Sheng Wu > > > SkyWalking, Shardingsphere and Zipkin > > > > > -- > > Sheng Wu > > SkyWalking, Shardingsphere and Zipkin > >
Re: [PROPOSAL] Mesher supports skywalking
Interesting proposal. Could you explain a little more about the topology? And what do you expect after the integration? Sheng Willem Jiang 于2019年10月14日 周一上午10:06写道： > I think we can get some feedback from the skywalking community, so I just > forward the mail to dev@skywalking > BTW, you find the topology map here[1] > [1] > > https://issues.apache.org/jira/secure/attachment/12982640/12982640_image-2019-10-10-15-05-02-666.png > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Fri, Oct 11, 2019 at 10:45 AM 陈硕 <814464...@qq.com> wrote: > > > Hello, everyone > >Skywalking is a very popular application performance management > > software. We can enhance the performance management capability of mesher > by > > accessing skywalking. > >Now I accessed skywalking using the manual-SDK go2sky( > > https://github.com/tetratelabs/go2sky) recommended by the official > > website . Unlike java-sdk , the SDK of golang need manually create and > end > > span to send messages to the skywalking server. Now I'm ready to adjust > the > > code. I want to put the code in the proxy/pkg directory. Create an APM > > management directory and use go2sky as a client. > > > > Skywalking draws Mehser's topology as follows： > > > > Looking forward to your suggestions. > > > > -- > > 陈硕 > > 邮箱：814464...@qq.com > > > > > -- Sheng Wu SkyWalking, Shardingsphere and Zipkin
