Prashant Srivastava

Hi @khpeet and @jmpf2019 Thanks for opening this feature request. Adding support for W3C in the AWS Lambda instrumentation is on our backlog, however I cannot provide and ETA for...

Hi @tanaka-takayoshi Can you provide a simple repro code or a code snippet of your lambda function demonstrating the instrumentation? Also, what's the .Net runtime you're using for your function?

Hi @iain-raidiam MongoDB instrumentation is currently not on X-Ray SDK's roadmap and I can't give an ETA for it at the moment. As a potential workaround, you can use OpenTelemetry...

Hi @mikeparker Yes, right now all the Lambda platforms do not support propagation of trace header from SQS to a lambda function. We are hard at work on it. >Can...

Hi @mikeparker Since we cannot openly talk about the release date, I have asked the AWS support to reach out to you with the information. Thanks for your patience.

Hi @xrn The X-Ray team is working hard to get this support rolled out. We will update this issue once the feature is available. Thanks for being patient.

Hi @lorchda Thanks for providing the context. In your raw trace json, I do not even see the expected url for the `adoptions` db to be appended to the subsegment...

Hi @rui-wang-imprivata Since none of the lines from the stack trace are showing up in the exception, I believe [this line](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/3db9e60896ade16ae65464dccd4fd9676cc262d6/exporter/awsxrayexporter/internal/translator/cause.go#L459) in the stack trace translation could be the reason....

Hi @rui-wang-imprivata , Thanks for providing the repro code. I was able to see for myself that indeed the stacktrace isn't populating in the exported segment. And I was also...

> can we look into the Python instrumentation to see how it captures attributes? @willarmiros @lorchda Seems like the Python instrumentation of db clients is not recording the connection string...