fix(http): fully migrate to v2 schema and address reviewer feedback

Author: Dipanshusinghh

.chloggen/migrate-http-v2.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: http
+note: Migrate HTTP semantic conventions to Weaver v2 schema
+issues: [3809]

model/http/common.yaml

@@ -2,9 +2,7 @@ file_format: definition/2
 
 attribute_groups:
   - id: attributes.http.common
-    visibility: public
-    stability: development
-    brief: "Describes HTTP attributes."
+    visibility: internal
     attributes:
       - ref: http.request.method
         requirement_level: required
@@ -40,9 +38,7 @@ attribute_groups:
         examples: ['1.0', '1.1', '2', '3']
 
   - id: attributes.http.client
-    visibility: public
-    stability: development
-    brief: 'HTTP Client attributes'
+    visibility: internal
     attributes:
       - ref_group: attributes.http.common
       - ref: server.address
@@ -72,9 +68,7 @@ attribute_groups:
           The `url.template` MUST have low cardinality. It is not usually available on HTTP clients, but may be known by the application or specialized HTTP instrumentation.
 
   - id: attributes.http.server
-    visibility: public
-    stability: development
-    brief: 'HTTP Server attributes'
+    visibility: internal
     attributes:
       - ref_group: attributes.http.common
       - ref: http.route

model/http/deprecated/registry-deprecated.yaml

@@ -3,81 +3,73 @@ file_format: definition/2
 attributes:
   - key: http.method
     type: string
+    brief: 'Deprecated, use `http.request.method` instead.'
     stability: development
     deprecated:
       reason: renamed
       renamed_to: http.request.method
-      note: 'Replaced by `http.request.method`.'
-    brief: 'Deprecated, use `http.request.method` instead.'
+      note: "Replaced by http.request.method."
     examples: ["GET", "POST", "HEAD"]
-
   - key: http.status_code
     type: int
+    brief: 'Deprecated, use `http.response.status_code` instead.'
     stability: development
     deprecated:
       reason: renamed
       renamed_to: http.response.status_code
-      note: 'Replaced by `http.response.status_code`.'
-    brief: 'Deprecated, use `http.response.status_code` instead.'
+      note: "Replaced by http.response.status_code."
     examples: [200]
-
   - key: http.scheme
     type: string
+    brief: 'Deprecated, use `url.scheme` instead.'
     stability: development
     deprecated:
       reason: renamed
       renamed_to: url.scheme
-      note: 'Replaced by `url.scheme`.'
-    brief: 'Deprecated, use `url.scheme` instead.'
+      note: "Replaced by url.scheme."
     examples: ['http', 'https']
-
   - key: http.url
     type: string
+    brief: 'Deprecated, use `url.full` instead.'
     stability: development
     deprecated:
       reason: renamed
       renamed_to: url.full
-      note: 'Replaced by `url.full`.'
-    brief: 'Deprecated, use `url.full` instead.'
+      note: "Replaced by url.full."
     examples: ['https://www.foo.bar/search?q=OpenTelemetry#SemConv']
-
   - key: http.target
     type: string
+    brief: 'Deprecated, use `url.path` and `url.query` instead.'
     stability: development
     deprecated:
       reason: obsoleted
       note: Split to `url.path` and `url.query`.
-    brief: 'Deprecated, use `url.path` and `url.query` instead.'
     examples: ['/search?q=OpenTelemetry#SemConv']
-
   - key: http.request_content_length
     type: int
+    brief: 'Deprecated, use `http.request.header.content-length` instead.'
     stability: development
     deprecated:
       reason: uncategorized
       note: Replaced by `http.request.header.content-length`.
-    brief: 'Deprecated, use `http.request.header.content-length` instead.'
     examples: 3495
-
   - key: http.response_content_length
     type: int
+    brief: 'Deprecated, use `http.response.header.content-length` instead.'
     stability: development
     deprecated:
       reason: uncategorized
       note: Replaced by `http.response.header.content-length`.
-    brief: 'Deprecated, use `http.response.header.content-length` instead.'
     examples: 3495
-
   - key: http.client_ip
     type: string
     stability: development
     deprecated:
       reason: renamed
       renamed_to: client.address
-      note: 'Replaced by `client.address`.'
+      note: "Replaced by client.address."
     brief: "Deprecated, use `client.address` instead."
     examples: '83.164.160.102'
-
   - key: http.host
     type: string
     stability: development
@@ -87,42 +79,34 @@ attributes:
         Replaced by one of `server.address`, `client.address` or `http.request.header.host`, depending on the usage.
     brief: "Deprecated, use one of `server.address`, `client.address` or `http.request.header.host` instead, depending on the usage."
     examples: ['www.example.org']
-
   - key: http.request_content_length_uncompressed
-    type: int
     stability: development
     deprecated:
       reason: renamed
       renamed_to: http.request.body.size
-      note: 'Replaced by `http.request.body.size`.'
+      note: "Replaced by http.request.body.size."
+    type: int
     brief: "Deprecated, use `http.request.body.size` instead."
     examples: 5493
-
   - key: http.response_content_length_uncompressed
-    type: int
     stability: development
     deprecated:
       reason: renamed
       renamed_to: http.response.body.size
-      note: 'Replaced by `http.response.body.size`.'
+      note: "Replaced by http.response.body.size."
+    type: int
     brief: "Deprecated, use `http.response.body.size` instead."
     examples: 5493
-
   - key: http.server_name
     type: string
     stability: development
     deprecated:
       reason: renamed
       renamed_to: server.address
-      note: 'Replaced by `server.address`.'
+      note: "Replaced by server.address."
     brief: "Deprecated, use `server.address` instead."
     examples: ['example.com']
-
   - key: http.flavor
-    stability: development
-    deprecated:
-      reason: uncategorized
-      note: "Split into `network.protocol.name` and `network.protocol.version`"
     type:
       members:
         - id: http_1_0
@@ -150,15 +134,17 @@ attributes:
           brief: 'QUIC protocol.'
           stability: development
     brief: 'Deprecated, use `network.protocol.name` and `network.protocol.version` instead.'
-
+    deprecated:
+      reason: uncategorized
+      note: "Split into `network.protocol.name` and `network.protocol.version`"
+    stability: development
   - key: http.user_agent
     type: string
-    stability: development
+    brief: 'Deprecated, use `user_agent.original` instead.'
+    examples: ['CERN-LineMode/2.15 libwww/2.17b3',
+               'Mozilla/5.0 (iPhone; CPU iPhone OS 14_7_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Mobile/15E148 Safari/604.1']
     deprecated:
       reason: renamed
       renamed_to: user_agent.original
-      note: 'Replaced by `user_agent.original`.'
-    brief: 'Deprecated, use `user_agent.original` instead.'
-    examples:
-      - 'CERN-LineMode/2.15 libwww/2.17b3'
-      - 'Mozilla/5.0 (iPhone; CPU iPhone OS 14_7_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Mobile/15E148 Safari/604.1'
+      note: "Replaced by user_agent.original."
+    stability: development

model/http/events.yaml

@@ -1,4 +1,5 @@
 file_format: definition/2
+
 events:
   - name: http.client.request.exception
     stability: development
@@ -8,10 +9,13 @@ events:
       from completing successfully.
     note: >
       This event SHOULD be recorded when an exception occurs during HTTP client operations.
+
       Instrumentations SHOULD set the severity to WARN (severity number 13) when recording this event.
+
       Some HTTP client frameworks generate artificial exceptions for non-successful HTTP status codes
       (e.g., 404 Not Found). When possible, instrumentations SHOULD NOT record these artificial
       exceptions, or SHOULD set the severity to DEBUG (severity number 5).
+
       Instrumentations MAY provide a configuration option to populate exception events
       with the attributes captured on the corresponding HTTP client span.
     attributes:
@@ -22,6 +26,7 @@ events:
         requirement_level:
           conditionally_required: Required if `exception.type` is not set, recommended otherwise.
       - ref: exception.stacktrace
+
   - name: http.server.request.exception
     stability: development
     brief: >
@@ -30,7 +35,9 @@ events:
       the server from successfully handling the request.
     note: >
       This event SHOULD be recorded when an exception occurs during HTTP server request processing.
+
       Instrumentations SHOULD set the severity to ERROR (severity number 17) when recording this event.
+
       Instrumentations MAY provide a configuration option to populate exception events
       with the attributes captured on the corresponding HTTP server span.
     attributes: