You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the awsxray exporter is looking for X-Ray custom attribute keys when populating the queueURL and tableName properties during the translation between OTel and X-Ray formats. Some instrumentation libraries, such as the aws-sdk-go-v2/otelaws do not set the X-Ray custom attributes, but instead set the relevant Semantic Convention attributes. However, as the awsxray exporter is not looking for these attributes, the data is not translated and exported.
I recently raised a PR on the aws-sdk-go-v2/otelaws instrumentation library to add the X-Ray custom attributes, however, it was agreed that we should instead use the relevant semantic convention attributes instead and update the exporter to extract these values.
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/awsxray
Describe the issue you're reporting
Currently the
awsxray
exporter is looking for X-Ray custom attribute keys when populating thequeueURL
andtableName
properties during the translation between OTel and X-Ray formats. Some instrumentation libraries, such as theaws-sdk-go-v2/otelaws
do not set the X-Ray custom attributes, but instead set the relevant Semantic Convention attributes. However, as theawsxray
exporter is not looking for these attributes, the data is not translated and exported.I recently raised a PR on the
aws-sdk-go-v2/otelaws
instrumentation library to add the X-Ray custom attributes, however, it was agreed that we should instead use the relevant semantic convention attributes instead and update the exporter to extract these values.The text was updated successfully, but these errors were encountered: