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
{{ message }}
This repository has been archived by the owner on May 23, 2023. It is now read-only.
As it stands, the interfaces do not provide a way to access the trace id, nor the span id.
Jaeger client exposes span.trace_id and span.span_id, but if the tracer is not initialised, that obviously blows up, as the noop span doesn't have those attributes, requiring people to do hasattr checks.
It's useful to log the trace id/span id of the request being started, which can later be used to debug issues with the request somewhere downstream.
The text was updated successfully, but these errors were encountered:
As it stands, the interfaces do not provide a way to access the trace id, nor the span id.
Jaeger client exposes span.trace_id and span.span_id, but if the tracer is not initialised, that obviously blows up, as the noop span doesn't have those attributes, requiring people to do
hasattr
checks.It's useful to log the trace id/span id of the request being started, which can later be used to debug issues with the request somewhere downstream.
The text was updated successfully, but these errors were encountered: