Update old http semantic conventions

Author: heyams

articles/azure-monitor/app/java-standalone-telemetry-processors-examples.md

@@ -329,12 +329,12 @@ The following sample shows how to hash existing attribute values.
 ### Extract
 
 The following sample shows how to use a regular expression (regex) to create new attributes based on the value of another attribute.
-For example, given `http.url = http://example.com/path?queryParam1=value1,queryParam2=value2`, the following attributes are inserted:
+For example, given `url.path = http://example.com/path?queryParam1=value1,queryParam2=value2`, the following attributes are inserted:
 * httpProtocol: `http`
 * httpDomain: `example.com`
 * httpPath: `path`
 * httpQueryParams: `queryParam1=value1,queryParam2=value2`
-* http.url: *no* change
+* url.path: *no* change
 
 ```json
 {
@@ -345,7 +345,7 @@ For example, given `http.url = http://example.com/path?queryParam1=value1,queryP
         "type": "attribute",
         "actions": [
           {
-            "key": "http.url",
+            "key": "url.path",
             "pattern": "^(?<httpProtocol>.*):\\/\\/(?<httpDomain>.*)\\/(?<httpPath>.*)(\\?|\\&)(?<httpQueryParams>.*)",
             "action": "extract"
           }
@@ -358,7 +358,7 @@ For example, given `http.url = http://example.com/path?queryParam1=value1,queryP
 
 ### Mask
 
-For example, given `http.url = https://example.com/user/12345622` is updated to `http.url = https://example.com/user/****` using either of the below configurations.
+For example, given `url.path = https://example.com/user/12345622` is updated to `url.path = https://example.com/user/****` using either of the below configurations.
 
 
 First configuration example:
@@ -372,7 +372,7 @@ First configuration example:
         "type": "attribute",
         "actions": [
           {
-            "key": "http.url",
+            "key": "url.path",
             "pattern": "user\\/\\d+",
             "replace": "user\\/****",
             "action": "mask"
@@ -396,7 +396,7 @@ Second configuration example with regular expression group name:
         "type": "attribute",
         "actions": [
           {
-            "key": "http.url",
+            "key": "url.path",
             "pattern": "^(?<userGroupName>[a-zA-Z.:\/]+)\d+",
             "replace": "${userGroupName}**",
             "action": "mask"

articles/azure-monitor/app/java-standalone-telemetry-processors.md

@@ -397,11 +397,11 @@ This section lists some common span attributes that telemetry processors can use
 
 | Attribute  | Type | Description | 
 |---|---|---|
-| `http.method` | string | HTTP request method.|
-| `http.url` | string | Full HTTP request URL in the form `scheme://host[:port]/path?query[#fragment]`. The fragment isn't usually transmitted over HTTP. But if the fragment is known, it should be included.|
-| `http.status_code` | number | [HTTP response status code](https://tools.ietf.org/html/rfc7231#section-6).|
-| `http.flavor` | string | Type of HTTP protocol. |
-| `http.user_agent` | string | Value of the [HTTP User-Agent](https://tools.ietf.org/html/rfc7231#section-5.5.3) header sent by the client. |
+| `http.request.method` (used to be `http.method`) | string | HTTP request method.|
+| `url.full` (client span) or `url.path` (server span) (used to be `http.url`) | string | Full HTTP request URL in the form `scheme://host[:port]/path?query[#fragment]`. The fragment isn't usually transmitted over HTTP. But if the fragment is known, it should be included.|
+| `http.response.status_code` (used to be `http.status_code`) | number | [HTTP response status code](https://tools.ietf.org/html/rfc7231#section-6).|
+| `network.protocol.version` (used to be `http.flavor`) | string | Type of HTTP protocol. |
+| `user_agent.original` (used to be `http.user_agent`) | string | Value of the [HTTP User-Agent](https://tools.ietf.org/html/rfc7231#section-5.5.3) header sent by the client. |
 
 ### JDBC spans
 

articles/azure-monitor/app/java-standalone-upgrade-from-2x.md

@@ -85,9 +85,9 @@ The telemetry processors perform the following actions (in order):
    which means it applies to all telemetry that has attributes
    (currently `requests` and `dependencies`, but soon also `traces`).
 
-   It matches any telemetry that has attributes named `http.method` and `http.url`.
+   It matches any telemetry that has attributes named `http.request.method` (used to be `http.method`) and `url.path` (used to be `http.url`).
 
-   Then it extracts the path portion of the `http.url` attribute into a new attribute named `tempName`.
+   Then it extracts the path portion of the `url.path` attribute into a new attribute named `tempName`.
 
 2. The second telemetry processor is a span processor (has type `span`),
    which means it applies to `requests` and `dependencies`.
@@ -111,13 +111,13 @@ The telemetry processors perform the following actions (in order):
         "include": {
           "matchType": "strict",
           "attributes": [
-            { "key": "http.method" },
-            { "key": "http.url" }
+            { "key": "http.request.method" },
+            { "key": "url.path" }
           ]
         },
         "actions": [
           {
-            "key": "http.url",
+            "key": "url.path",
             "pattern": "https?://[^/]+(?<tempPath>/[^?]*)",
             "action": "extract"
           }
@@ -132,7 +132,7 @@ The telemetry processors perform the following actions (in order):
           ]
         },
         "name": {
-          "fromAttributes": [ "http.method", "tempPath" ],
+          "fromAttributes": [ "http.request.method", "tempPath" ],
           "separator": " "
         }
       },