wpessers
wpessers
Well yes, but also @gshpychka if you want changes to how these instrumentations work / which spans are exported with specific attributes etc. you’re looking in the wrong place. I...
> Hey @wpessers 👋 Unrelated to this PR, but I wasn't sure of a better way to reach you. I saw that you [submitted to join](https://hashicorp.github.io/terraform-provider-aws/#join-the-contributors-slack) our Slack channel, but...
Tbh, I already accepted that this PR was not going to get merged since maintainers are not showing any activity on it. But maybe now they see it's useful to...
@hc-github-team-terraform-aws
Makes a lot of sense in my opinion, yes.
Thanks for the suggestion @trentm! This points new users directly to the right place to get relevant information, ~hence I've updated the sidebar.~ I’ll be opening a PR on the...
Any opinions @open-telemetry/lambda-extension-approvers?
@serkan-ozal yes that’s what I found also, but wanted to check whether you all agreed on this change before opening a pr.
Is this not something that should be fixed in the propagator itself? i.e.: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/propagators/propagator-aws-xray-lambda https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/propagator/opentelemetry-propagator-aws-xray ...
Hi @gkaskonas that does indeed not sound right. I will try to reproduce your issue this weekend when I have some more time. Do you receive any other spans for...