Merge branch 'main' into decouple_shared_memory_metric

.chloggen/634.yaml

@@ -0,0 +1,25 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: messaging
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Add a GCP Pub/Sub unary pull example and the new GCP messaging attributes:
+- `messaging.gcp_pubsub.message.ack_deadline`,
+- `messaging.gcp_pubsub.message.ack_id`,
+- `messaging.gcp_pubsub.message.delivery_attempt`"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [527]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

.chloggen/735.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: db
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add `db.client.operation.duration` metric
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [512]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

.chloggen/910.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: db
+note: Reorganize DB conventions to be shared across span and metric conventions.
+issues: [ 910 ]

.chloggen/911.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: db
+note: Rename `db.name` and `db.redis.database_index` to `db.namespace`, deprecate `db.mssql.instance_name`.
+issues: [ 885 ]

.chloggen/931.yaml

@@ -0,0 +1,7 @@
+change_type: enhancement
+
+component: http
+
+note: List all HTTP client and server attributes in the corresponding table, remove common attributes from yaml and markdown.
+
+issues: [928]

.chloggen/db_metrics.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: breaking
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: db
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Rename `pool.name` to `db.client.connections.pool.name` and `state` to `db.client.connections.state`.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [909]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

.chloggen/device_app_lifecycle.yaml

@@ -0,0 +1,26 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: breaking
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: device.app.lifecycle
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: >
+  Reformat and update the `device.app.lifecycle` event description adds constraints for the possible values of
+  the `android.state` and `ios.state`.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [794]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext: >
+  Removes the `ios.lifecycle.events` and `android.lifecycle.events` attributes from the global registry and adds
+  constraints for the possible values of the `android.state` and `ios.state` attributes.

.github/CODEOWNERS

@@ -76,11 +76,15 @@
 
 # .NET semantic conventions approvers
 /model/metrics/dotnet/ @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
-/docs/dotnet/          @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
+/model/registry/aspnetcore.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
+/model/registry/signalr.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
+/docs/dotnet/ @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
+/docs/attributes-registry/aspnetcore.md @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
+/docs/attributes-registry/signalr.md @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-dotnet-approver  @open-telemetry/semconv-http-approvers
 
 # Gen-AI semantic conventions approvers
-/model/registry/gen-ai.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers 
-/model/metrics/gen-ai.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers 
+/model/registry/gen-ai.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers
+/model/metrics/gen-ai.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers
 /model/trace/gen-ai.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers
 /docs/gen-ai/ @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers
 /docs/attributes-registry/llm.md @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-llm-approvers

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -20,6 +20,7 @@ body:
         # DO NOT manually edit it.
         # Start semconv area list
         - area:android
+        - area:aspnetcore
         - area:aws
         - area:browser
         - area:client
@@ -46,8 +47,8 @@ body:
         - area:heroku
         - area:host
         - area:http
-        - area:ios
         - area:k8s
+        - area:log
         - area:messaging
         - area:network
         - area:oci
@@ -60,6 +61,7 @@ body:
         - area:server
         - area:service
         - area:session
+        - area:signalr
         - area:source
         - area:system
         - area:telemetry

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -13,6 +13,7 @@ body:
         # DO NOT manually edit it.
         # Start semconv area list
         - area:android
+        - area:aspnetcore
         - area:aws
         - area:browser
         - area:client
@@ -39,8 +40,8 @@ body:
         - area:heroku
         - area:host
         - area:http
-        - area:ios
         - area:k8s
+        - area:log
         - area:messaging
         - area:network
         - area:oci
@@ -53,6 +54,7 @@ body:
         - area:server
         - area:service
         - area:session
+        - area:signalr
         - area:source
         - area:system
         - area:telemetry

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -22,6 +22,7 @@ body:
         # DO NOT manually edit it.
         # Start semconv area list
         - area:android
+        - area:aspnetcore
         - area:aws
         - area:browser
         - area:client
@@ -48,8 +49,8 @@ body:
         - area:heroku
         - area:host
         - area:http
-        - area:ios
         - area:k8s
+        - area:log
         - area:messaging
         - area:network
         - area:oci
@@ -62,6 +63,7 @@ body:
         - area:server
         - area:service
         - area:session
+        - area:signalr
         - area:source
         - area:system
         - area:telemetry

.gitignore

@@ -7,6 +7,7 @@
 .project
 .settings
 bin
+.vs
 
 # NetBeans
 /.nb-gradle

.markdown_link_check_config.json

@@ -2,6 +2,9 @@
   "ignorePatterns": [
     {
       "pattern": "^https://github\\.com/open-telemetry/opentelemetry-specification/(issues|pull)"
+    },
+    {
+      "pattern": "^https://github\\.com/open-telemetry/semantic-conventions/(issues|pull)"
     }
   ],
   "replacementPatterns": [

.vscode/settings.json

@@ -11,7 +11,7 @@
     },
     "yaml.schemas": {
         "https://raw.githubusercontent.com/open-telemetry/build-tools/v0.24.0/semantic-conventions/semconv.schema.json": [
-            "model/**/*.yaml",
+            "model/**/*.yaml"
         ]
     },
     "json.schemaDownload.enable": true

docs/attributes-registry/README.md

@@ -55,6 +55,7 @@ Currently, the following namespaces exist:
 * [HTTP](http.md)
 * [iOS](ios.md)
 * [K8s](k8s.md)
+* [Log](log.md)
 * [Network](network.md)
 * [OCI](oci.md)
 * [OpenTelemetry](otel.md)

docs/attributes-registry/android.md

@@ -3,23 +3,24 @@
 <!-- toc -->
 
 - [Android Attributes](#android-attributes)
-- [Android Lifecycle Event Attributes](#android-lifecycle-event-attributes)
+- [Deprecated Android Attributes](#deprecated-android-attributes)
 
 <!-- tocstop -->
 
 ## Android Attributes
+
 <!-- semconv registry.android(omit_requirement_level) -->
 | Attribute  | Type | Description  | Examples  | Stability |
 |---|---|---|---|---|
 | `android.os.api_level` | string | Uniquely identifies the framework API revision offered by a version (`os.version`) of the android operating system. More information can be found [here](https://developer.android.com/guide/topics/manifest/uses-sdk-element#ApiLevels). | `33`; `32` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 <!-- endsemconv -->
 
-## Android Lifecycle Event Attributes
+## Deprecated Android Attributes
 
-<!-- semconv registry.android.lifecycle.events(omit_requirement_level) -->
+<!-- semconv registry.android.deprecated(omit_requirement_level) -->
 | Attribute  | Type | Description  | Examples  | Stability |
 |---|---|---|---|---|
-| `android.state` | string | This attribute represents the state the application has transitioned into at the occurrence of the event. [1] | `created` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| `android.state` | string | Deprecated use the `device.app.lifecycle` event definition including `android.state` as a payload field instead. [1] | `created` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 
 **[1]:** The Android lifecycle states are defined in [Activity lifecycle callbacks](https://developer.android.com/guide/components/activities/activity-lifecycle#lc), and from which the `OS identifiers` are derived.
 

docs/attributes-registry/aspnetcore.md

@@ -0,0 +1,46 @@
+# ASP.NET Core
+
+<!-- toc -->
+
+- [ASP.NET Core Attributes](#aspnet-core-attributes)
+
+<!-- tocstop -->
+
+## ASP.NET Core Attributes
+
+<!-- semconv registry.aspnetcore(omit_requirement_level) -->
+| Attribute  | Type | Description  | Examples  | Stability |
+|---|---|---|---|---|
+| `aspnetcore.rate_limiting.result` | string | Rate-limiting result, shows whether the lease was acquired or contains a rejection reason | `acquired`; `request_canceled` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.diagnostics.handler.type` | string | Full type name of the [`IExceptionHandler`](https://learn.microsoft.com/dotnet/api/microsoft.aspnetcore.diagnostics.iexceptionhandler) implementation that handled the exception. | `Contoso.MyHandler` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.diagnostics.exception.result` | string | ASP.NET Core exception middleware handling result | `handled`; `unhandled` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.rate_limiting.policy` | string | Rate limiting policy name. | `fixed`; `sliding`; `token` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.request.is_unhandled` | boolean | Flag indicating if request was handled by the application pipeline. | `True` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.routing.is_fallback` | boolean | A value that indicates whether the matched route is a fallback route. | `True` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aspnetcore.routing.match_status` | string | Match result - success or failure | `success`; `failure` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+
+`aspnetcore.rate_limiting.result` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+| Value  | Description | Stability |
+|---|---|---|
+| `acquired` | Lease was acquired | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `endpoint_limiter` | Lease request was rejected by the endpoint limiter | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `global_limiter` | Lease request was rejected by the global limiter | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `request_canceled` | Lease request was canceled | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+
+`aspnetcore.diagnostics.exception.result` MUST be one of the following:
+
+| Value  | Description | Stability |
+|---|---|---|
+| `handled` | Exception was handled by the exception handling middleware. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `unhandled` | Exception was not handled by the exception handling middleware. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `skipped` | Exception handling was skipped because the response had started. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `aborted` | Exception handling didn't run because the request was aborted. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+
+`aspnetcore.routing.match_status` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+| Value  | Description | Stability |
+|---|---|---|
+| `success` | Match succeeded | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+| `failure` | Match failed | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
+<!-- endsemconv -->