-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Span ID always null in Logs | Logs ID injection #1962
Comments
Would you mind trying to put together a reproduction case with a minimal sanic app? I'm wondering if something is breaking down with the contextvar propagation or something, but I haven't seen this behavior. |
Thanks for such quick response!! Sure, pls allow me some time to get a simple app. I would also love to help in fixing anything broken |
I have two questions:
Thanks! |
It's possible. The most likely culprit would be changes to You could try the following code snippet from within your app to see if you can properly fetch the current transaction and span: from elasticapm.traces import execution_context
t = execution_context.get_transaction()
s = execution_context.get_span() |
Describe the bug: I am using logging support which injects correlation ids (trace, transaction, span). However even after running with 100% sample rate I've not been able to get a single log with a Span ID!
Also "maybe" this could be the reason that I am not seeing any logs in trace waterfall
To Reproduce
Environment (please complete the following information)
elastic-apm==6.7.1
Additional context
N/A
The text was updated successfully, but these errors were encountered: