[chore] Move Peer to registry (#853)

Co-authored-by: Joao Grassi <[email protected]>

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -48,6 +48,7 @@ body:
         - area:network
         - area:oci
         - area:os
+        - area:peer
         - area:process
         - area:rpc
         - area:server

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -41,6 +41,7 @@ body:
         - area:network
         - area:oci
         - area:os
+        - area:peer
         - area:process
         - area:rpc
         - area:server

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -50,6 +50,7 @@ body:
         - area:network
         - area:oci
         - area:os
+        - area:peer
         - area:process
         - area:rpc
         - area:server

docs/attributes-registry/README.md

@@ -54,6 +54,7 @@ Currently, the following namespaces exist:
 * [Network](network.md)
 * [OCI](oci.md)
 * [OS](os.md)
+* [Peer](peer.md)
 * [Process](process.md)
 * [RPC](rpc.md)
 * [Server](server.md)

docs/attributes-registry/peer.md

@@ -0,0 +1,12 @@
+<!--- Hugo front matter used to generate the website version of this page:
+--->
+
+# Peer
+
+## Peer Attributes
+
+<!-- semconv registry.peer(omit_requirement_level) -->
+| Attribute  | Type | Description  | Examples  | Stability |
+|---|---|---|---|---|
+| `peer.service` | string | The [`service.name`](/docs/resource/README.md#service) of the remote service. SHOULD be equal to the actual `service.name` resource attribute of the remote service if any. | `AuthTokenCache` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+<!-- endsemconv -->

docs/general/attributes.md

@@ -296,7 +296,7 @@ Instrumentations SHOULD provide a way for users to configure this name.
 <!-- semconv peer -->
 | Attribute  | Type | Description  | Examples  | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
 |---|---|---|---|---|---|
-| `peer.service` | string | The [`service.name`](/docs/resource/README.md#service) of the remote service. SHOULD be equal to the actual `service.name` resource attribute of the remote service if any. | `AuthTokenCache` | `Recommended` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`peer.service`](../attributes-registry/peer.md) | string | The [`service.name`](/docs/resource/README.md#service) of the remote service. SHOULD be equal to the actual `service.name` resource attribute of the remote service if any. | `AuthTokenCache` | `Recommended` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 <!-- endsemconv -->
 
 Examples of `peer.service` that users may specify:

model/general.yaml

@@ -32,14 +32,8 @@ groups:
     type: span
     brief: "Operations that access some remote service."
     attributes:
-      - id: service
-        type: string
-        stability: experimental
-        brief: >
-          The [`service.name`](/docs/resource/README.md#service)
-          of the remote service. SHOULD be equal to the actual `service.name`
-          resource attribute of the remote service if any.
-        examples: "AuthTokenCache"
+      - ref: peer.service
+        requirement_level: recommended
   - id: identity
     type: span
     brief: >

model/registry/peer.yaml

@@ -0,0 +1,15 @@
+groups:
+  - id: registry.peer
+    type: span
+    prefix: peer
+    brief: >
+      Operations that access some remote service.
+    attributes:
+      - id: service
+        type: string
+        stability: experimental
+        brief: >
+          The [`service.name`](/docs/resource/README.md#service)
+          of the remote service. SHOULD be equal to the actual `service.name`
+          resource attribute of the remote service if any.
+        examples: "AuthTokenCache"