We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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-xray-propagator
I was experiencing some difficulties getting the Lambda Xray generated traces to connect to the otel generated spans via the otel java wrapper.
Issue described here: open-telemetry/opentelemetry-lambda#1669
I noticed that the following SPI file has both the xray and xray-lambda propagator registered: io.opentelemetry.sdk.autoconfigure.spi.internal.ComponentProvider
However this file only has the xray propagator registered: io.opentelemetry.sdk.autoconfigure.spi.ConfigurablePropagatorProvider
Is that intended or is this a bug?
N/A
1.42.0-alpha
No response
The text was updated successfully, but these errors were encountered:
@jack-berg I saw that you were the author of both files, so you may have context on this
Sorry, something went wrong.
Talked to Tyler on the issue linked in the description. I will be submitting a PR to add the xray-lambda propagator to the following file io.opentelemetry.sdk.autoconfigure.spi.ConfigurablePropagatorProvider
PR is merged, closing issue.
srprash
wangzlei
No branches or pull requests
Component(s)
aws-xray-propagator
What happened?
Description
I was experiencing some difficulties getting the Lambda Xray generated traces to connect to the otel generated spans via the otel java wrapper.
Issue described here: open-telemetry/opentelemetry-lambda#1669
I noticed that the following SPI file has both the xray and xray-lambda propagator registered: io.opentelemetry.sdk.autoconfigure.spi.internal.ComponentProvider
However this file only has the xray propagator registered: io.opentelemetry.sdk.autoconfigure.spi.ConfigurablePropagatorProvider
Is that intended or is this a bug?
Steps to Reproduce
N/A
Expected Result
N/A
Actual Result
N/A
Component version
1.42.0-alpha
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: