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
kavirajk
changed the title
tracing: Jaeger/Opentracing client libs are depreicated, use opentelmetry for instrumentation instead
tracing: Jaeger/Opentracing client libs are depreicated, use opentelemetry for instrumentation instead
Jul 31, 2022
kavirajk
changed the title
tracing: Jaeger/Opentracing client libs are depreicated, use opentelemetry for instrumentation instead
tracing: Jaeger/Opentracing client libs are deprecated, use opentelemetry for instrumentation instead
Jul 31, 2022
kavirajk
changed the title
tracing: Jaeger/Opentracing client libs are deprecated, use opentelemetry for instrumentation instead
tracing: Jaeger/Opentracing are deprecated, use open-telemetry for instrumentation instead
Aug 15, 2022
Looking forward to see this implemented, I realized that Grafana sends trace headers in w3c format to Loki which it can't support due to the feature not being implemented in the jaeger libraries. OCD was triggered as I wanted Grafana, Loki and Thanos to all support tracing.
Currently Loki is instrumented with
opentracing/jaeger
client libraries for tracing.This instrumentation comes from weaveworks/common package and dskit's spanlogger package.
Those client libraries(opentracing, jaeger) are deprecated in the favor of opentelemetry client sdk. It's better to migrate.
I hope, It should be completely possible to migrate underlying dependencies without changing any API of those packages.
Example of using otel tracing client libraries for instrumentation in Go is here.
The text was updated successfully, but these errors were encountered: