[Monitor OpenTelemetry Exporter] Filter OpenTelemetry Semantic Attributes from Being Double Recorded (#33322)

### Packages impacted by this PR
@azure/monitor-opentelemetry-exporter

### Describe the problem that is addressed by this PR
Known OpenTelemetry HTTP semantic attributes should not be double
recorded in the Application Insights attributes as well as in custom
dimensions.

### Are there test cases added in this PR? _(If not, why?)_
Yes, updated to ensure that OpenTelemetry HTTP semantic attributes are
not recorded as custom dimensions.

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)

---------

Co-authored-by: Copilot <[email protected]>

Author: JacksonWeber

sdk/monitor/monitor-opentelemetry-exporter/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Release History
 
+## 1.0.0-beta.30 ()
+
+### Other Changes
+
+- Filter OpenTelemetry semantic attributes from being double recorded as custom dimensions.
 ## 1.0.0-beta.29 (2025-03-04)
 
 ### Features Added

sdk/monitor/monitor-opentelemetry-exporter/src/types.ts

@@ -28,13 +28,22 @@ import {
   SEMATTRS_EXCEPTION_MESSAGE,
   SEMATTRS_EXCEPTION_STACKTRACE,
   SEMATTRS_EXCEPTION_TYPE,
+  SEMATTRS_HTTP_FLAVOR,
   SEMATTRS_HTTP_HOST,
   SEMATTRS_HTTP_METHOD,
   SEMATTRS_HTTP_ROUTE,
+  SEMATTRS_HTTP_SCHEME,
   SEMATTRS_HTTP_STATUS_CODE,
+  SEMATTRS_HTTP_TARGET,
   SEMATTRS_HTTP_URL,
+  SEMATTRS_HTTP_USER_AGENT,
+  SEMATTRS_NET_HOST_IP,
+  SEMATTRS_NET_HOST_NAME,
+  SEMATTRS_NET_HOST_PORT,
   SEMATTRS_NET_PEER_IP,
   SEMATTRS_NET_PEER_NAME,
+  SEMATTRS_NET_PEER_PORT,
+  SEMATTRS_NET_TRANSPORT,
   SEMATTRS_PEER_SERVICE,
   SEMATTRS_RPC_GRPC_STATUS_CODE,
   SEMATTRS_RPC_SYSTEM,
@@ -128,13 +137,14 @@ export enum MaxPropertyLengths {
 export const legacySemanticValues = [
   SEMATTRS_NET_PEER_IP,
   SEMATTRS_NET_PEER_NAME,
+  SEMATTRS_NET_HOST_IP,
   SEMATTRS_PEER_SERVICE,
+  SEMATTRS_HTTP_USER_AGENT,
   SEMATTRS_HTTP_METHOD,
   SEMATTRS_HTTP_URL,
   SEMATTRS_HTTP_STATUS_CODE,
   SEMATTRS_HTTP_ROUTE,
   SEMATTRS_HTTP_HOST,
-  SEMATTRS_HTTP_URL,
   SEMATTRS_DB_SYSTEM,
   SEMATTRS_DB_STATEMENT,
   SEMATTRS_DB_OPERATION,
@@ -144,6 +154,14 @@ export const legacySemanticValues = [
   SEMATTRS_EXCEPTION_TYPE,
   SEMATTRS_EXCEPTION_MESSAGE,
   SEMATTRS_EXCEPTION_STACKTRACE,
+  SEMATTRS_HTTP_SCHEME,
+  SEMATTRS_HTTP_TARGET,
+  SEMATTRS_HTTP_FLAVOR,
+  SEMATTRS_NET_TRANSPORT,
+  SEMATTRS_NET_HOST_NAME,
+  SEMATTRS_NET_HOST_PORT,
+  SEMATTRS_NET_PEER_PORT,
+  "http.status_text",
 ];
 
 /**

sdk/monitor/monitor-opentelemetry-exporter/test/internal/spanUtils.spec.ts

@@ -28,6 +28,7 @@ import {
   SEMATTRS_HTTP_HOST,
   SEMATTRS_HTTP_METHOD,
   SEMATTRS_HTTP_ROUTE,
+  SEMATTRS_HTTP_SCHEME,
   SEMATTRS_HTTP_STATUS_CODE,
   SEMATTRS_HTTP_URL,
   SEMATTRS_NET_PEER_IP,
@@ -587,6 +588,7 @@ describe("spanUtils.ts", () => {
           [SEMATTRS_HTTP_ROUTE]: "/api/example",
           [SEMATTRS_HTTP_URL]: "https://example.com/api/example",
           [SEMATTRS_HTTP_STATUS_CODE]: 200,
+          [SEMATTRS_HTTP_SCHEME]: "https",
           "extra.attribute": "foo",
         });
         span.setStatus({
@@ -910,6 +912,7 @@ describe("spanUtils.ts", () => {
           [SEMATTRS_HTTP_URL]: "https://example.com/api/example",
           [SEMATTRS_PEER_SERVICE]: "https://someotherexample.com/api/example",
           [SEMATTRS_HTTP_STATUS_CODE]: 200,
+          [SEMATTRS_HTTP_SCHEME]: "https",
           "extra.attribute": "foo",
         });
         span.setStatus({