[
https://issues.apache.org/jira/browse/KUDU-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853838#comment-17853838
]
Alexey Serbin commented on KUDU-2782:
-------------------------------------
It's been a while, and the OpenTracing project has been sunset as of now, and
[OpenTelemetry|https://opentelemetry.io/] emerged out of OpenTracing and
OpenCensus. The need for distributed tracing in Kudu still stays as is, and
many projects added support for OpenTelemetry at this point. When implementing
this, it makes sense to take a look at [already existing integrations with
OpenTelemetry|https://opentelemetry.io/ecosystem/integrations/].
> Implement distributed tracing support in Kudu
> ---------------------------------------------
>
> Key: KUDU-2782
> URL: https://issues.apache.org/jira/browse/KUDU-2782
> Project: Kudu
> Issue Type: Task
> Components: ops-tooling
> Reporter: Mike Percy
> Priority: Major
> Labels: hackathon, roadmap-candidate, supportability
>
> It would be useful to implement distributed tracing support in Kudu,
> especially something like OpenTracing support that we could use with Zipkin,
> Jaeger, DataDog, etc. Particularly useful would be auto-sampled and on-demand
> traces of write RPCs since that would help us identify slow nodes or hotspots
> in the replication group and troubleshoot performance and stability issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
