Replace Jaeger Client with OpenTelemetry SDK #1156
Comments
tfcace
added a commit
to tfcace/cadence-client
that referenced
this issue
May 10, 2022
Related issue: uber-go#1156
tfcace
added a commit
to tfcace/cadence-client
that referenced
this issue
May 10, 2022
Related issue: uber-go#1156
tfcace
added a commit
to tfcace/cadence-client
that referenced
this issue
May 10, 2022
Related issue: uber-go#1156
tfcace
added a commit
to tfcace/cadence-client
that referenced
this issue
Dec 14, 2022
Related issue: uber-go#1156
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The Jaeger clients are being deprecated in favor of OpenTelemetry SDKs.
Proposed Solution
Allow the Cadence SDK to utilize the Go Otel SDK to continue sending traces to Jaeger, but make it easier to
instrument Workflows to other tracing platforms that are Otel compatible.
Additional context
Notice on the official page for Jaeger clients. Here.
The text was updated successfully, but these errors were encountered: