Area(s)

area:peer

What's missing?

The peer.service attribute does not match the way we define the identity of services in the service.* namespace via service.name and service.namespace.

Part of this issue was also brought up as #2338

Describe the solution you'd like

Add service.peer.{name|namespace} to the service.* namespace for spans.

Other options considered, and discarded, were:

• introduce peer.service.name and peer.service.namespace with the intention of supporting match the usage of service.namespace + service.name as identity for services.
• "special-casing" this to avoid breaking OpenTracing users by allowing peer.service to have a special syntax to represent combinations of service.namespace + service.name. However, I know from experience that some organizations already use / in their peer.service to represent the operation used on the invoked service.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}