Merge branch 'main' into process-fields

.chloggen/1006.yaml

@@ -0,0 +1,13 @@
+change_type: breaking
+
+component: messaging
+
+note: |
+  Support generic operations in messaging and rename metrics:
+
+    - Make `messaging.operation.name` required and `messaging.operation.type` conditionally required when type is applicable.
+    - Rename `messaging.publish.messages` metric to `messaging.client.published.messages`
+    - Unify `messaging.publish.duration` and `messaging.receive.duration` metrics into `messaging.client.operation.duration`
+    - Unify `messaging.receive.messages` and `messaging.process.messages` metrics into `messaging.client.consumed.messages`
+
+issues: [1006, 947, 937]

.chloggen/1087.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: gen-ai
+note: Use GenAI instead of LLM on GenAI trace semantic conventions and minor cleanups.
+issues: [1087]

.chloggen/1120.yaml

@@ -0,0 +1,12 @@
+change_type: breaking
+
+component: db
+
+note: |
+  Clean up `db.system` enum members:
+
+  - remove `firstsql`, `mssqlcompact`, and `cloudscape` as the corresponding databases are discontinued.
+  - rename `cache` to `intersystems_cache`
+  - remove `coldfusion` as it is not a database.
+
+issues: [1110]

.chloggen/1168.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: messaging
+note: Clarify how per-message attributes should be recorded for batch operations.
+issues: [ 1168 ]

.chloggen/1169.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: messaging
+note: Define sampling relevant attributes for messaging client spans
+issues: [ 432, 1169 ]

.chloggen/815.yaml

@@ -0,0 +1,8 @@
+change_type: breaking
+component: messaging
+note: >
+  Introduce common attributes for consumer group and subscription name instead of per-system ones:
+  - `messaging.consumer.group.name` instead of `messaging.kafka.consumer.group`, `messaging.rocketmq.client_group`, and `messaging.eventhubs.consumer.group`.
+  - `messaging.destination.subscription.name` instead of `messaging.servicebus.destination.subscription_name`. Use it in the Google Pub/Sub conventions.
+
+issues: [ 815 ]

.chloggen/839.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: gen-ai
+note: Adding `gen_ai.request.top_k`, `gen_ai.request.presence_penalty`,  `gen_ai.request.frequency_penalty` and `gen_ai.request.stop_sequences` attributes.
+issues: [839]

.chloggen/942.yaml

@@ -0,0 +1,4 @@
+change_type: enhancement
+component: messaging
+note: Document `messaging.operation.name` for Azure messaging systems.
+issues: [942]

.chloggen/align_es_spec.yaml

@@ -0,0 +1,24 @@
+# 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: >
+  Align Elasticsearch span name to the general database span name guidelines.
+  Deprecates `db.elasticsearch.cluster.name` in favor of `db.namespace`.
+
+# 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: [1002]
+
+# (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/db_sanitization.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: Specify sanitization for `db.query.text`.
+
+# 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: [717]
+
+# (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/gcp-client-libraries.yaml

@@ -0,0 +1,4 @@
+change_type: 'enhancement'
+component: gcp
+note: Introduces `gcp.client.service` scope attribute.
+issues: [ 1047 ]

.github/CODEOWNERS

@@ -37,7 +37,7 @@
 /model/registry/http.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
 /model/registry/server.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
 /model/registry/client.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
-/model/registry/network.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
+/model/registry/network.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers @open-telemetry/semconv-security-approvers
 /model/registry/error.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
 /model/registry/url.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
 /model/registry/user-agent.yaml   @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-http-approvers
@@ -76,4 +76,16 @@
 /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
 
+# Security semantic conventions approvers
+/model/registry/file.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+/model/registry/dns.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+/model/registry/process.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+/model/registry/tls.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+/model/registry/user.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+
+/model/metrics/dns.yaml @open-telemetry/specs-semconv-approvers @open-telemetry/semconv-security-approvers
+/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/workflows/stale-pr.yml

@@ -12,7 +12,7 @@ jobs:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           stale-pr-message: 'This PR was marked stale due to lack of activity. It will be closed in 7 days.'
           close-pr-message: 'Closed as inactive. Feel free to reopen if this PR is still being worked on.'
-          exempt-pr-labels: 'bug,work in progress,experts needed'
+          exempt-pr-labels: 'bug,work in progress,experts needed,never stale'
           exempt-draft-pr: true
           # opt out of defaults to avoid marking issues as stale
           days-before-stale: -1