Moving to OpenTelemetry or accepting other tracers

[youssofatepsor]

Is your feature request related to a problem? Please describe.
openTracing/opentracer-go was archived on 05/23/2023, but Cadence is still using it in WorkerOptions:

import (
  "github.com/opentracing/opentracing-go"
)

type WorkerOptions struct {
  Tracer opentracing.Tracer
}

Today, we cannot use the v2 library for Datadog’s tracers because Datadog removed support for OpenTracing (OpenTracing merged with OpenCensus to form OpenTelemetry). This also raises security concerns, as we are relying on libraries that are no longer maintained, both for Datadog and OpenTracing.

Proposed Solution
Consider switching from OpenTracing to OpenTelemetry, or allow users to choose their own tracer library.

[natemort]

@shijiesheng are you familiar with what would be required to support opentelemetry?

[youssofatepsor]

Any news on this ?

[demirkayaender]

Hi! We won't move by default but supporting OpenTelemetry is a good idea. Currently every maintainer is working on a different project so this might give us two options:

• If you are interested, we can provide help about how to add the OpenTelemetry support but you might need to implement it.
• The other option is to wait probably till this summer, we will have more bandwidth at that time.

Does this work?