Update aws lambda spec to remove X-Ray Env propagation#3166
Update aws lambda spec to remove X-Ray Env propagation#3166carlosalberto merged 11 commits intoopen-telemetry:mainfrom
Conversation
Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators. We also decided that `EventToCarrier` should be specified in the spec to improve cross language instrumentation consistency.
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Tristan Sloughter <t@crashfast.com>
Pulled section about EventToCarrier for further discussion.
|
@Aneurysm9 note: I pulled the section about |
|
fyi @tedsuo we have a spec reviewer block here |
|
Approved by AWS Lambdas SME's - @Aneurysm9 |
|
No GCP or Azure SME input required |
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
…ambda.md Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
…ambda.md Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
|
This has enough approvals but merging is blocked because there are unresolved conversations. |
|
@tigrannajaryan thanks for the call-out. I've resolved the remaining conversation. Should be good to go! |
ad7244f to
7c30584
Compare
7c30584 to
744bb9f
Compare
open-telemetry/opentelemetry-specification#3166 Per discussion in the FAAS SIG, we decided that the AWS X-Ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
…7970) open-telemetry/opentelemetry-specification#3166 Per discussion in the FAAS SIG, we decided that the AWS X-Ray environment variable should be moved to a span link to avoid interfering with the configured propagators. Also related to #5167.
May I know the deeper reason why changing parent-child to be links? |
|
@wangzlei This PR is probably not the best place to have this discussion. Can I suggest you open a new issue or join the FAAS SIG meeting? The quick summary is that the prior behavior would break traces for other vendors when x-ray was enabled because the x-ray internal spans were not available. |
|
@wangzlei As Tyler said, please open an issue in https://github.com/open-telemetry/semantic-conventions (and maybe join the FaaS call? We meet every Thursday at 8am Pacific) |
…y#3166) * Update aws lambda spec to remove X-Ray Env propagation Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
…y#3166) * Update aws lambda spec to remove X-Ray Env propagation Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
We also decided thatEventToCarriershould be specified in the spec to improve cross language instrumentation consistency.I removed
EventToCarrierfrom this PR to focus on the x-ray propagation. We can revisit in a separate PR.Fixes #3060