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
Sorry for the late response, but looking over the linked issue on opentelemetry-rust, it seems like the short-term solution might be open-telemetry/opentelemetry-rust#1394, but I think a longer-term solution would require some sort of API on tracing_subscriber::fmt's end.
(I'll close this for now, but let me know if this should be re-opened.)
@ewoolsey did you ever find a workaround for this? I see you're collecting both logs and traces, how are you correlating them? I've spend a while trying to figure it out to no avail, any help would be much appreciated.
Please see this issue for more context
When looking at the output of the logging pipeline, the
Trace ID
field is blank for all logs emitted inside a function marked by#[instrument]
This does not emit a trace id
But this does
I'm not sure exactly what's going wrong under the hood.
Here is my initial setup
The text was updated successfully, but these errors were encountered: