Enhance Observability with support of OpenTelemetry

[hanyuancheung]

What would you like to be added

As the migration of OpenTracing and OpenCensus, OpenTelemetry becomes the standard in the observability field. I've checked the related module in dubbo-go(including dubbo-go-sample), and now still use OpenTracing to exporter trace signal to Jaeger or Zipkin backend, as well as use Prometheus to exporter metrics signal to backend.

Proposed Solution

I wonder if you guys like to integrate the ability of the OpenTelemetry, package into the independent module, which is for the use of external users, code structure like below:

• observability
  • tracing
  • metrics
  • other signals

Alternatives

Because opentelemetry-collector-contrib provides all different kinds of receivers, so users could deploy collector component by using like jaegerreceiver or zipkinreceiver, and the data model is transformed from OpenTracing to OpenTelemetry automatically.
I do not know which way dubbo-go community prefer.
If the former way looks good, I'll work on it to provide an OpenTelemetry version module. If latter, I'll add doc or readme to let users know how to use OpenTracing to export trace and metrics into OpenTelemetry backend.

[hanyuancheung]

@AlexStocks PTAL.

[AlexStocks]

@AlexStocks PTAL.

I prefer the former solution. So pls add an solution to integrate the OpenTelemetry into dubbogo.

[XiaoWeiKIN]

mark

[AlexStocks]

@hanyuancheung how is this task going now?

[LaurenceLiZhixin]

cc @pherzheyu

[pherzheyu]

OpenTelemetry trace is already a stable feature. Going on.

[hanyuancheung]

@hanyuancheung how is this task going now?

Yeah, I've been working on it. Sorry that I've been slowed down by being too busy recently. I'll finish it as soon as possible.

cc @pherzheyu @AlexStocks