-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Awsxray exporter requires OTLP trace id to be xray compatible trace Id #24389
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
The issue with this is that X-Ray requires the first 8 hex digits to be a timestamp, specifically the timestamp at which the trace was started. |
@dhilgarth is right, and that's why it is must for the x-ray format trace id to be generated in the instrumentation. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
From comments, I'm going to close this issue as this requested functionality is not possible. Please let me know if I've misunderstood. |
Component(s)
exporter/awsxray
Is your feature request related to a problem? Please describe.
We are using the awsxray exporter to send traces to AWS X-Ray backend but the exporter is not able to translate the span from OTLP format due to invalid xray trace id.
Other people have encounter this problem: open-telemetry/opentelemetry-cpp#1259
Describe the solution you'd like
I think the awsxray exporter should generate a new xray trace id and incorporate the original trace id from OTLP into the xray trace format. This solution wouldn't require the client to generate the xray compatible trace id. Also the instrumentation library doesn't need to change to accommodate this.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: