Merge branch 'main' into process-fields

.chloggen/1102.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: gen-ai
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add GenAI model server metrics for measuring LLM serving latency
+
+# 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: [1102]
+
+# (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/1155.yaml

@@ -0,0 +1,4 @@
+change_type: bug_fix
+component: messaging
+note: Update Kafka Spring example to align with the messaging spec
+issues: [ 1155 ]

.chloggen/1156.yaml

@@ -0,0 +1,7 @@
+change_type: breaking
+
+component: messaging
+
+note: Rename `messaging.kafka.message.offset` to `messaging.kafka.offset`
+
+issues: [1156]

.chloggen/1165.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: Clarify that `db.query.parameter.<key>` is string representation of the parameter value
+
+# 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: [ 1165 ]
+
+# (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/1166.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: Sampling relevant attributes defined for database client spans
+
+# 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: [ 1019 ]
+
+# (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/1167.yaml

@@ -0,0 +1,4 @@
+change_type: bug_fix
+component: http
+note: "Relax requirement on when to set HTTP span status to Error from `MUST` to `SHOULD`."
+issues: [1167, 1003]

.chloggen/1200.yaml

@@ -0,0 +1,6 @@
+change_type: enhancement
+component: gen_ai
+note: >
+  Rename `gen_ai.usage.prompt_tokens` to `gen_ai.usage.input_tokens` and `gen_ai.usage.completion_tokens` to `gen_ai.usage.output_tokens`
+  to align terminology between spans and metrics.
+issues: [ 1200 ]

.chloggen/1202.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: gen_ai
+note: Convert `gen_ai.operation.name` to enum and use it on spans
+issues: [ 1202 ]

.chloggen/1239.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: network
+note: Add QUIC to the list of well known network transports
+issues: [ 1237, 1239 ]

.chloggen/1241.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: messaging
+note: Deprecate `messaging.destination_publish.*`` namespace and remove all usages.
+issues: [ 1178, 1241 ]

.chloggen/1243.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: "`db.query.text` IN-clauses MAY be collapsed during the sanitization process"
+
+# 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: [ 1053 ]
+
+# (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/1244.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: db, messaging
+note: Clarify that DB and messaging system-specific conventions override common ones
+issues: [ 1235, 1244 ]

.chloggen/cloud-events-restructure.yaml

@@ -0,0 +1,5 @@
+change_type: 'enhancement'
+component: cloudevents
+note: CloudEvents conventions to follow HTTP/Messaging Span conventions
+issues: [654]
+subtext:

.chloggen/log-original-body.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: log
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add 'log.record.original' attribute.
+
+# 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: [1137]
+
+# (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/merge_cpu_states.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: system
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Rename `process.cpu.state`, `container.cpu.state`, and `system.cpu.state` attributes into a common `cpu.mode` attribute
+
+# 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: [840]
+
+# (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/nodejs-metrics.yaml

@@ -0,0 +1,17 @@
+# 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: new_component
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: nodejs
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Introducing semantic conventions for Node.js runtime metrics.
+
+# 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: [990]

.chloggen/v8js-metrics.yaml

@@ -0,0 +1,17 @@
+# 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: new_component
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: v8js
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Introducing semantic conventions for V8 JS Engine runtime metrics.
+
+# 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: [990]

.github/CODEOWNERS

@@ -87,5 +87,3 @@
 /model/metrics/process-metrics.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
 /model/resource/process.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
 /model/network.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
-
-# TODO - Add semconv area experts

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -28,6 +28,7 @@ body:
         - area:cloudevents
         - area:code
         - area:container
+        - area:cpu
         - area:db
         - area:deployment
         - area:destination
@@ -71,6 +72,7 @@ body:
         - area:url
         - area:user-agent
         - area:user
+        - area:v8js
         - area:webengine
         # End semconv area list
   - type: textarea

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -21,6 +21,7 @@ body:
         - area:cloudevents
         - area:code
         - area:container
+        - area:cpu
         - area:db
         - area:deployment
         - area:destination
@@ -64,6 +65,7 @@ body:
         - area:url
         - area:user-agent
         - area:user
+        - area:v8js
         - area:webengine
         # End semconv area list
   - type: textarea

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -30,6 +30,7 @@ body:
         - area:cloudevents
         - area:code
         - area:container
+        - area:cpu
         - area:db
         - area:deployment
         - area:destination
@@ -73,6 +74,7 @@ body:
         - area:url
         - area:user-agent
         - area:user
+        - area:v8js
         - area:webengine
         # End semconv area list
   - type: textarea

CHANGELOG.md

@@ -26,7 +26,7 @@
 - `device.app.lifecycle`: Reformat and update the `device.app.lifecycle` event description adds constraints for the possible values of the `android.state` and `ios.state`.
  (#794)
   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.
-  
+
 - `messaging`: Rename `messaging.client_id` to `messaging.client.id` (#935)
 - `rpc`: Rename`message.*` attributes under `rpc` to `rpc.message.*`. Deprecate old `message.*` attributes. (#854)
 
@@ -51,7 +51,7 @@
   The entirety of the registry now is generated using weaver with templates
   under the `templates/` directory.  Snippets still require a hardcoded
   command.
-  
+
 - `http`: List all HTTP client and server attributes in the corresponding table, remove common attributes from yaml and markdown. (#928)
 - `other`: Document patterns and suggestions for semconv code generation. (#551, #953)
 - `db`: Show applicable common attributes in individual database semantic conventions. (#973)
@@ -72,14 +72,6 @@
 - `net`: Add previously deprecated net attributes to registry (#1029)
   These attributes were deprecated in 1.13
 
-## Unreleased
-
-### Breaking
-
-### Features
-
-### Fixes
-
 ## v1.25.0
 
 ### 🛑 Breaking changes 🛑

CONTRIBUTING.md

@@ -83,7 +83,7 @@ environment configured:
 ### 1. Modify the YAML model
 
 Refer to the
-[Semantic Convention YAML Language](https://github.com/open-telemetry/build-tools/blob/v0.24.0/semantic-conventions/syntax.md)
+[Semantic Convention YAML Language](https://github.com/open-telemetry/build-tools/blob/v0.25.0/semantic-conventions/syntax.md)
 to learn how to make changes to the YAML files.
 
 #### Schema files

Makefile

@@ -13,8 +13,8 @@ CHLOGGEN_CONFIG  := .chloggen/config.yaml
 
 # see https://github.com/open-telemetry/build-tools/releases for semconvgen updates
 # Keep links in model/README.md and .vscode/settings.json in sync!
-SEMCONVGEN_VERSION=0.24.0
-WEAVER_VERSION=0.2.0
+SEMCONVGEN_VERSION=0.25.0
+WEAVER_VERSION=0.5.0
 
 # From where to resolve the containers (e.g. "otel/weaver").
 CONTAINER_REPOSITORY=docker.io

docs/attributes-registry/README.md

@@ -40,6 +40,7 @@ Currently, the following namespaces exist:
 - [CloudEvents](cloudevents.md)
 - [Code](code.md)
 - [Container](container.md)
+- [CPU](cpu.md)
 - [Db](db.md)
 - [Deployment](deployment.md)
 - [Destination](destination.md)
@@ -85,6 +86,7 @@ Currently, the following namespaces exist:
 - [URL](url.md)
 - [User](user.md)
 - [User Agent](user-agent.md)
+- [V8js](v8js.md)
 - [Webengine](webengine.md)
 
 [developers recommendations]: ../general/attribute-naming.md#recommendations-for-application-developers

docs/attributes-registry/android.md

@@ -6,8 +6,8 @@
 
 # Android
 
-- [Android](#android-attributes)
-- [Android Deprecated](#android-deprecated-attributes)
+- [Android Attributes](#android-attributes)
+- [Deprecated Android Attributes](#deprecated-android-attributes)
 
 ## Android Attributes
 
@@ -17,7 +17,7 @@ The Android platform on which the Android application is running.
 | ---------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | ---------------------------------------------------------------- |
 | `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) |
 
-## Android Deprecated Attributes
+## Deprecated Android Attributes
 
 This document defines attributes that represents an occurrence of a lifecycle transition on the Android platform.
 

docs/attributes-registry/aspnetcore.md

@@ -6,7 +6,7 @@
 
 # Aspnetcore
 
-## Aspnetcore Attributes
+## ASP.NET Core Attributes
 
 ASP.NET Core attributes