[chore] Move Session to registry (#843)

Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com>

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -53,6 +53,7 @@ body:
         - area:rpc
         - area:server
         - area:service
+        - area:session
         - area:source
         - area:thread
         - area:tls

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -46,6 +46,7 @@ body:
         - area:rpc
         - area:server
         - area:service
+        - area:session
         - area:source
         - area:thread
         - area:tls

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -55,6 +55,7 @@ body:
         - area:rpc
         - area:server
         - area:service
+        - area:session
         - area:source
         - area:thread
         - area:tls

docs/attributes-registry/README.md

@@ -59,6 +59,7 @@ Currently, the following namespaces exist:
 * [RPC](rpc.md)
 * [Server](server.md)
 * [Service](service.md)
+* [Session](session.md)
 * [Source](source.md)
 * [Thread](thread.md)
 * [TLS](tls.md)

docs/attributes-registry/session.md

@@ -0,0 +1,13 @@
+<!--- Hugo front matter used to generate the website version of this page:
+--->
+
+# Session
+
+## Session Attributes
+
+<!-- semconv registry.session(omit_requirement_level) -->
+| Attribute  | Type | Description  | Examples  | Stability |
+|---|---|---|---|---|
+| `session.id` | string | A unique id to identify a session. | `00112233-4455-6677-8899-aabbccddeeff` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| `session.previous_id` | string | The previous `session.id` for this user, when known. | `00112233-4455-6677-8899-aabbccddeeff` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+<!-- endsemconv -->

docs/general/session.md

@@ -20,8 +20,8 @@ backends can link the two sessions.
 <!-- semconv session-id -->
 | Attribute  | Type | Description  | Examples  | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
 |---|---|---|---|---|---|
-| `session.id` | string | A unique id to identify a session. | `00112233-4455-6677-8899-aabbccddeeff` | `Opt-In` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
-| `session.previous_id` | string | The previous `session.id` for this user, when known. | `00112233-4455-6677-8899-aabbccddeeff` | `Opt-In` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`session.id`](../attributes-registry/session.md) | string | A unique id to identify a session. | `00112233-4455-6677-8899-aabbccddeeff` | `Opt-In` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| [`session.previous_id`](../attributes-registry/session.md) | string | The previous `session.id` for this user, when known. | `00112233-4455-6677-8899-aabbccddeeff` | `Opt-In` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 <!-- endsemconv -->
 
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/document-status.md

model/registry/session.yaml

@@ -0,0 +1,26 @@
+groups:
+  - id: registry.session
+    prefix: session
+    type: attribute_group
+    brief: >
+      Session is defined as the period of time encompassing all activities performed by the application and the actions
+      executed by the end user.
+
+      Consequently, a Session is represented as a collection of Logs, Events, and Spans emitted by the Client Application
+      throughout the Session's duration. Each Session is assigned a unique identifier, which is included as an attribute in
+      the Logs, Events, and Spans generated during the Session's lifecycle.
+
+      When a session reaches end of life, typically due to user inactivity or session timeout, a new session identifier
+      will be assigned. The previous session identifier may be provided by the instrumentation so that telemetry
+      backends can link the two sessions.
+    attributes:
+      - id: id
+        type: string
+        stability: experimental
+        brief: "A unique id to identify a session."
+        examples: "00112233-4455-6677-8899-aabbccddeeff"
+      - id: previous_id
+        type: string
+        stability: experimental
+        brief: "The previous `session.id` for this user, when known."
+        examples: "00112233-4455-6677-8899-aabbccddeeff"

model/session.yaml

@@ -14,15 +14,7 @@ groups:
       will be assigned. The previous session identifier may be provided by the instrumentation so that telemetry
       backends can link the two sessions.
     attributes:
-      - id: id
-        type: string
-        stability: experimental
-        brief: "A unique id to identify a session."
-        examples: "00112233-4455-6677-8899-aabbccddeeff"
+      - ref: session.id
         requirement_level: opt_in
-      - id: previous_id
-        type: string
-        stability: experimental
-        brief: "The previous `session.id` for this user, when known."
-        examples: "00112233-4455-6677-8899-aabbccddeeff"
+      - ref: session.previous_id
         requirement_level: opt_in