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
Is your feature request related to a problem?
Should we be capturing topic ARNs as messaging.destination instead of name, we loose information about the account, region the topic belongs to by using just the name. This additional information is helpful in locating the topic
Describe the solution you'd like
We already have handle to arn in the boto-core instrumentation extension for SNS. If it makes sense, we should use arn as the value of messaging.destination attribute capture arn
Also considered adding account and region information of the topic to the span attributes, but there are no semantics defined to specify these values
Alternate Solution:
Instead of modifying the existing attribute, account information related to the topic can be included as an additional span attribute. However, it's important to note that there are currently no defined semantics for specifying the value. Something like ....
Suggested attribute: aws.account.id:12343441
open-telemetry/opentelemetry-js-contrib#1716
Is your feature request related to a problem?
Should we be capturing topic ARNs as
messaging.destination
instead of name, we loose information about the account, region the topic belongs to by using just the name. This additional information is helpful in locating the topicDescribe the solution you'd like
We already have handle to arn in the boto-core instrumentation extension for SNS. If it makes sense, we should use arn as the value of
messaging.destination
attribute capture arnAlso considered adding account and region information of the topic to the span attributes, but there are no semantics defined to specify these values
Alternate Solution:
Instead of modifying the existing attribute, account information related to the topic can be included as an additional span attribute. However, it's important to note that there are currently no defined semantics for specifying the value. Something like ....
Suggested attribute:
aws.account.id:12343441
cc: @svrnm @noltak3 @yumarg
The text was updated successfully, but these errors were encountered: