-
Notifications
You must be signed in to change notification settings - Fork 302
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
AWS Lambda support for extraction of W3C trace headers sent over http #343
Comments
I'm also experiencing the same issue with a project I'm working with. Hope this can be solved soon. |
hey @srprash - is there any progress on this? Thanks! |
Hi @srprash, same as previous comment ^, checking if there's any progress on this. |
This should now be implemented by #408, check the release notes of 1.1.0-beta.2 here: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.AWSLambda/CHANGELOG.md |
Can someone with permissions please close this issue? See my previous comment. |
Closing per @Oberon00 comment. |
Issue with OpenTelemetry.Contrib.Instrumentation.AWSLambda
List of all OpenTelemetry NuGet
packages and version that you are
using (e.g.
OpenTelemetry 1.0.2
):Runtime version (e.g.
net462
,net48
,netcoreapp3.1
,net6.0
etc. You canfind this information from the
*.csproj
file):netcoreapp3.1
Is this a feature request or a bug?
What is the expected behavior?
Incoming http W3C trace headers are extracted and added to the active span created. Currently only headers from X-Ray are extracted according to the comments in this method.
What is the actual behavior?
I am sending
traceparent
andtracestate
headers from a client SPA to an AWS dotnetcore3.1 Lambda using this wrapper. Currently the trace context sent via HTTP headers are not automatically extracted via this wrapper, thus I have reverted to not use this wrapper and am manually creating my own Spans/extraction of context.The text was updated successfully, but these errors were encountered: