Merge branch 'main' into cf-resource

Signed-off-by: Karsten Schnitter <k.schnitter@sap.com>

# Conflicts:
#	docs/attributes-registry/README.md

.chloggen/700.yaml → .chloggen/564.yaml

@@ -7,14 +7,14 @@
 change_type: enhancement
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: messaging
+component: process
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add a "Process" spans and metrics for messaging
+note: Add additional attributes to process attribute registry
 
 # 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: [657]
+issues: [564]
 
 # (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.

.chloggen/814.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: messaging
+note: Adds `messaging.destination.partition.id`` to the messaging attributes
+issues: [ 814 ]

.chloggen/862.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: exception
+note: Replace constraints with requirement levels on exceptions.
+issues: [ 862 ]

.chloggen/863.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: process
+note: Replace constraints with requirement_level in process attributes.
+issues: [ 863 ]

.chloggen/866.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: db
+note: Rename `db.statement` to `db.query.text` and introduce `db.query.parameter.<key>`
+issues: [ 716 ]

.chloggen/870.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: db
+note: Renames `db.sql.table`, `db.cassandra.table`, `db.mongodb.collection`, and `db.cosmosdb.container` attributes to `db.collection.name`
+issues: [ 870 ]

.chloggen/875.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: db
+note: Rename `db.operation` to `db.operation.name`.
+issues: [ 884 ]

.chloggen/890.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: messaging
+note: Rename `messaging.operation` to `messaging.operation.type`, add `messaging.operation.name`.
+issues: [ 890 ]

.chloggen/894.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: db
+note: Deprecate the `db.user` attribute.
+issues: [ 885 ]

.chloggen/804.yaml → .chloggen/first-gen-ai.yaml

@@ -4,17 +4,17 @@
 # your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: new_component
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: http
+component: gen-ai
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Two fixes to the HTTP semconv migration guide
+note: Introducing semantic conventions for GenAI clients.
 
 # 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: [ 802 ]
+issues: [327]
 
 # (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.

.chloggen/509.yaml → .chloggen/rpc_registry.yaml

@@ -4,17 +4,17 @@
 # your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
+change_type: breaking
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: messaging
+component: rpc
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Clarify producer span relationships for messaging semantic conventions
+note: Rename`message.*` attributes under `rpc` to `rpc.message.*`. Deprecate old `message.*` attributes.
 
 # 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: [509]
+issues: [854]
 
 # (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.

.github/CODEOWNERS

@@ -78,4 +78,11 @@
 /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
 
+# 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/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
+
 # TODO - Add semconv area experts