hanyuancheung opened a new issue #1774: URL: https://github.com/apache/dubbo-go/issues/1774
<!-- Please only use this template for submitting enhancement requests --> ### What would you like to be added As the migration of OpenTracing and OpenCensus, [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-go) becomes the standard in the observability field. I've checked the related module in dubbo-go(including [dubbo-go-sample](https://github.com/apache/dubbo-go-samples/tree/master/tracing)), 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](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver) 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
