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
However the resulting segments and subsegments only include the operation field. The table_name field which is filled by v1 instrumentation is missing from V2 segments:
Sorry for bringing this sorry for the inconvenience. Currently, both OpenTelemetry and XRay do not support AWS service specific attributes in AWS SDK for Go v2 instrumentation. This feature is on our backlog but does not have a concrete schedule yet. A complete solution would involve covering all AWS service operations through configuration, similar to the AWS SDK for Go v1 instrumentation.
For DynamoDB(and SQS), there is a temporary solution available through OpenTelemetry. So, if you only need the DynamoDB table name, you can consider options:
migrate to OpenTelemetry.
customize your AWS SDK v2 instrumentation by copying OpenTelemtry code into XRay SDK.
Ok, thank you for your answer. I'll consider using one of the temporary solutions. However having this feature in the future release without any workarounds would obviously be great, so please consider this ticket a feature request.
I use the following function to instrument the
github.com/aws/aws-sdk-go-v2/aws
config of DynamoDB:However the resulting segments and subsegments only include the
operation
field. Thetable_name
field which is filled by v1 instrumentation is missing from V2 segments:The text was updated successfully, but these errors were encountered: