You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accordingly to the bug report, this manifests in recent versions of the opentelemetry-rust stack, while tracing-opentelemetry 0.24.x using opentelemetry* 0.23 works as intended.
On the other hand, it's not imperative to use the tracing framework to produce telemetry events, I only intended to do it as a filtered layer in #670 for convenience: the opentelemetry::global API is comparatively more clunky.
How should we solve this problem?
Pin tracing-opentelemetry crate at 0.24 and opentelemetry* at 0.23
0%
Implement telemetry directly using the opentelemetry::global API.
100%
Try to debug the issue further with hope of solving it upstream or finding a workaround.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've run into an issue with integrating OpenTelemetry with the tracing framework: tokio-rs/tracing-opentelemetry#159 (comment)
Accordingly to the bug report, this manifests in recent versions of the opentelemetry-rust stack, while tracing-opentelemetry 0.24.x using opentelemetry* 0.23 works as intended.
On the other hand, it's not imperative to use the tracing framework to produce telemetry events, I only intended to do it as a filtered layer in #670 for convenience: the
opentelemetry::globalAPI is comparatively more clunky.1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions