To Mr lxd, Thank you for your wonderful thoughts.
And any suggestion from everyone of dubbo/dubbogo community is welcome. 原始邮件 发件人: lxd-best<[email protected]> 收件人: dev<[email protected]> 发送时间: 2019年7月10日(周三) 20:10 主题: Discussion of monitor & calling chain trace solution for dubbo-go Hi: the attachment is the flow chart for dubbogo trace function At 2019-07-08 19:01:02, "xinming he" <[email protected]<mailto:[email protected]>> wrote: >oh，that sounds great. Let me study it first. >TKS. > >Ian Luo <[email protected]<mailto:[email protected]>> 于2019年7月8日周一 上午10:34写道： > >> +1 to adopting opentracing api. For tracing system, I suggest we should >> support Jeager first, and then Zipkin and Skywalking. >> >> On Mon, Jul 1, 2019 at 9:52 AM 望哥 >> <[email protected]<mailto:[email protected]>> wrote: >> >> > how about https://github.com/opentracing/opentracing-go , >> > it's Vendor-neutral APIs and instrumentation for distributed tracing, >> > supported by zipkin, skywalking, elaticsearch, etc. >> > >> > On Fri, Jun 28, 2019 at 4:45 PM xinming he >> > <[email protected]<mailto:[email protected]>> wrote: >> > >> > > Hi dubbogo community, >> > > We are going to start writing code for monitor & calling chain >> trace >> > > supporting for dubbo-go. >> > > Firstly, about monitor solution, I learned from @Huxing Zhang that >> > > dubbo will change dubbo-monitor based on alibaba/metrics. And >> prometheus >> > > will be supported by alibaba/metrics . So can we just definition the >> > > monitor interface (which called extension in dubbo-go) and implement >> > > prometheus >> > > as our first monitoring solution ? >> > > Secondly, about calling chain trace solution. There are many >> > wonderful >> > > trace system such as zipkin, skywalking and cat which widely used by >> many >> > > companies. Though dubbo have not support calling chain tracing system >> in >> > > project, we know there are projects have supported zipkin and >> skywalking >> > > in dubbo ecosystem . As for Golang , we know jeager maybe the best >> > solution >> > > now. So let me know what you think about it, should we support calling >> > > chain trace next ? And which calling chain trace system should be >> > > supported first ? >> > > >> > > Yours. >> > > Vito He @github.com/hxmhlt >> > > >> > >> > >> > -- >> > Regards, >> > 望哥 >> > >> > -------------------------------------------------------- >> > http://sisopipo.com/blog >> > >>
