Hi all: I'm forwarding a discussion about monitoring and tracing from the Dubbo community, I guess some of us may be interested in this, please subscribe and join that thread if so.
IIRC, the Dubbo agent in SkyWalking is based on dubbo-monitor, > 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 . I'll follow up this to see whether there're incompatible changes in the dubbo-monitor, which may affect the Dubbo agent in SkyWalking -------- Forwarding messages -------- From: "xinming he" <[email protected]> Date: 2019-06-28 16:45:19 To: [email protected] Subject: Discussion of monitor & calling chain trace solution for dubbo-go 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
