From 01c542ccacd869ee8a329aa33c65fb2c47bf2815 Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Sat, 3 Aug 2024 00:59:05 +0900 Subject: [PATCH] Prepare release v1.27.0 (#1307) --- .chloggen/1006.yaml | 13 - .chloggen/1024.yaml | 4 - .chloggen/1069.yaml | 7 - .chloggen/1070.yaml | 22 - .chloggen/1087.yaml | 4 - .chloggen/1102.yaml | 22 - .chloggen/1110.yaml | 7 - .chloggen/1120.yaml | 12 - .chloggen/1125.yaml | 22 - .chloggen/1155.yaml | 4 - .chloggen/1156.yaml | 7 - .chloggen/1165.yaml | 22 - .chloggen/1166.yaml | 22 - .chloggen/1167.yaml | 4 - .chloggen/1168.yaml | 4 - .chloggen/1169.yaml | 4 - .chloggen/1200.yaml | 6 - .chloggen/1202.yaml | 4 - .chloggen/1216.yaml | 5 - .chloggen/1239.yaml | 4 - .chloggen/1241.yaml | 4 - .chloggen/1243.yaml | 22 - .chloggen/1244.yaml | 4 - .chloggen/1289.yaml | 4 - .chloggen/1296.yaml | 4 - .chloggen/1297.yaml | 4 - .chloggen/811.yaml | 4 - .chloggen/815.yaml | 8 - .chloggen/839.yaml | 4 - .chloggen/942.yaml | 4 - .chloggen/abbr.yaml | 22 - .chloggen/add-azure-logs.yaml | 22 - .chloggen/add-pulsar-message-system.yaml | 22 - .chloggen/add_linux_memory_slab.yaml | 22 - .chloggen/align_es_spec.yaml | 24 - .chloggen/cicd-reg-attr.yaml | 24 - .chloggen/cloud-events-restructure.yaml | 5 - .chloggen/database-batch-operations.yaml | 22 - .chloggen/db_sanitization.yaml | 22 - .chloggen/extend-gen-ai-system-values.yaml | 22 - .chloggen/gcp-client-libraries.yaml | 4 - .chloggen/go-runtime-metrics.yaml | 22 - .chloggen/influxdb.yaml | 22 - .../jvm_memory-buffer_metric_renaming.yaml | 22 - .chloggen/log-original-body.yaml | 22 - .chloggen/merge_cpu_states.yaml | 22 - .chloggen/nodejs-metrics.yaml | 17 - .chloggen/session_start_end_event.yaml | 22 - .chloggen/user_ns.yaml | 22 - .chloggen/v8js-metrics.yaml | 17 - CHANGELOG.md | 84 +++ schema-next.yaml | 5 +- schemas/1.27.0 | 505 ++++++++++++++++++ 53 files changed, 592 insertions(+), 662 deletions(-) delete mode 100644 .chloggen/1006.yaml delete mode 100644 .chloggen/1024.yaml delete mode 100644 .chloggen/1069.yaml delete mode 100644 .chloggen/1070.yaml delete mode 100644 .chloggen/1087.yaml delete mode 100755 .chloggen/1102.yaml delete mode 100644 .chloggen/1110.yaml delete mode 100644 .chloggen/1120.yaml delete mode 100644 .chloggen/1125.yaml delete mode 100644 .chloggen/1155.yaml delete mode 100644 .chloggen/1156.yaml delete mode 100644 .chloggen/1165.yaml delete mode 100644 .chloggen/1166.yaml delete mode 100644 .chloggen/1167.yaml delete mode 100644 .chloggen/1168.yaml delete mode 100644 .chloggen/1169.yaml delete mode 100644 .chloggen/1200.yaml delete mode 100644 .chloggen/1202.yaml delete mode 100644 .chloggen/1216.yaml delete mode 100644 .chloggen/1239.yaml delete mode 100644 .chloggen/1241.yaml delete mode 100644 .chloggen/1243.yaml delete mode 100644 .chloggen/1244.yaml delete mode 100644 .chloggen/1289.yaml delete mode 100644 .chloggen/1296.yaml delete mode 100644 .chloggen/1297.yaml delete mode 100644 .chloggen/811.yaml delete mode 100644 .chloggen/815.yaml delete mode 100644 .chloggen/839.yaml delete mode 100644 .chloggen/942.yaml delete mode 100755 .chloggen/abbr.yaml delete mode 100644 .chloggen/add-azure-logs.yaml delete mode 100755 .chloggen/add-pulsar-message-system.yaml delete mode 100755 .chloggen/add_linux_memory_slab.yaml delete mode 100755 .chloggen/align_es_spec.yaml delete mode 100755 .chloggen/cicd-reg-attr.yaml delete mode 100755 .chloggen/cloud-events-restructure.yaml delete mode 100644 .chloggen/database-batch-operations.yaml delete mode 100755 .chloggen/db_sanitization.yaml delete mode 100755 .chloggen/extend-gen-ai-system-values.yaml delete mode 100755 .chloggen/gcp-client-libraries.yaml delete mode 100644 .chloggen/go-runtime-metrics.yaml delete mode 100644 .chloggen/influxdb.yaml delete mode 100755 .chloggen/jvm_memory-buffer_metric_renaming.yaml delete mode 100755 .chloggen/log-original-body.yaml delete mode 100755 .chloggen/merge_cpu_states.yaml delete mode 100755 .chloggen/nodejs-metrics.yaml delete mode 100755 .chloggen/session_start_end_event.yaml delete mode 100755 .chloggen/user_ns.yaml delete mode 100644 .chloggen/v8js-metrics.yaml create mode 100644 schemas/1.27.0 diff --git a/.chloggen/1006.yaml b/.chloggen/1006.yaml deleted file mode 100644 index a0216241ce..0000000000 --- a/.chloggen/1006.yaml +++ /dev/null @@ -1,13 +0,0 @@ -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] diff --git a/.chloggen/1024.yaml b/.chloggen/1024.yaml deleted file mode 100644 index d4d2a34b7d..0000000000 --- a/.chloggen/1024.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: db -note: List SQL database systems on the SQL semantic conventions. -issues: [1024] diff --git a/.chloggen/1069.yaml b/.chloggen/1069.yaml deleted file mode 100644 index 24a7720e98..0000000000 --- a/.chloggen/1069.yaml +++ /dev/null @@ -1,7 +0,0 @@ -change_type: enhancement - -component: db - -note: 'Update database span name: clarify that target depends on the operation and should not be set when corresponding data is not available.' - -issues: [1045] diff --git a/.chloggen/1070.yaml b/.chloggen/1070.yaml deleted file mode 100644 index bdab30dadf..0000000000 --- a/.chloggen/1070.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: Mention how to capture collection and operation names from query text in the 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: [ 1070 ] - -# (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: diff --git a/.chloggen/1087.yaml b/.chloggen/1087.yaml deleted file mode 100644 index d25ede66de..0000000000 --- a/.chloggen/1087.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: gen-ai -note: Use GenAI instead of LLM on GenAI trace semantic conventions and minor cleanups. -issues: [1087] diff --git a/.chloggen/1102.yaml b/.chloggen/1102.yaml deleted file mode 100755 index b80789491d..0000000000 --- a/.chloggen/1102.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/1110.yaml b/.chloggen/1110.yaml deleted file mode 100644 index c77c2f482d..0000000000 --- a/.chloggen/1110.yaml +++ /dev/null @@ -1,7 +0,0 @@ -change_type: enhancement - -component: other - -note: "Don't render deprecated enum members in semconv tables." - -issues: [1110] diff --git a/.chloggen/1120.yaml b/.chloggen/1120.yaml deleted file mode 100644 index c8129f3811..0000000000 --- a/.chloggen/1120.yaml +++ /dev/null @@ -1,12 +0,0 @@ -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] diff --git a/.chloggen/1125.yaml b/.chloggen/1125.yaml deleted file mode 100644 index e5f68d29a6..0000000000 --- a/.chloggen/1125.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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 `db.client.connections.*` attributes to `db.client.connection.*` - -# 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: [ 1125 ] - -# (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: diff --git a/.chloggen/1155.yaml b/.chloggen/1155.yaml deleted file mode 100644 index 4b71d69ec3..0000000000 --- a/.chloggen/1155.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: bug_fix -component: messaging -note: Update Kafka Spring example to align with the messaging spec -issues: [ 1155 ] diff --git a/.chloggen/1156.yaml b/.chloggen/1156.yaml deleted file mode 100644 index 56ef916b8e..0000000000 --- a/.chloggen/1156.yaml +++ /dev/null @@ -1,7 +0,0 @@ -change_type: breaking - -component: messaging - -note: Rename `messaging.kafka.message.offset` to `messaging.kafka.offset` - -issues: [1156] diff --git a/.chloggen/1165.yaml b/.chloggen/1165.yaml deleted file mode 100644 index 76e5ed376f..0000000000 --- a/.chloggen/1165.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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.` 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: diff --git a/.chloggen/1166.yaml b/.chloggen/1166.yaml deleted file mode 100644 index 2202ecc8d1..0000000000 --- a/.chloggen/1166.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/1167.yaml b/.chloggen/1167.yaml deleted file mode 100644 index cc9655329e..0000000000 --- a/.chloggen/1167.yaml +++ /dev/null @@ -1,4 +0,0 @@ -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] diff --git a/.chloggen/1168.yaml b/.chloggen/1168.yaml deleted file mode 100644 index 1ba4683655..0000000000 --- a/.chloggen/1168.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: messaging -note: Clarify how per-message attributes should be recorded for batch operations. -issues: [ 1168 ] diff --git a/.chloggen/1169.yaml b/.chloggen/1169.yaml deleted file mode 100644 index 33c7de4a91..0000000000 --- a/.chloggen/1169.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: messaging -note: Define sampling relevant attributes for messaging client spans -issues: [ 432, 1169 ] diff --git a/.chloggen/1200.yaml b/.chloggen/1200.yaml deleted file mode 100644 index 9d40d16961..0000000000 --- a/.chloggen/1200.yaml +++ /dev/null @@ -1,6 +0,0 @@ -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 ] diff --git a/.chloggen/1202.yaml b/.chloggen/1202.yaml deleted file mode 100644 index 32e4265029..0000000000 --- a/.chloggen/1202.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: gen_ai -note: Convert `gen_ai.operation.name` to enum and use it on spans -issues: [ 1202 ] diff --git a/.chloggen/1216.yaml b/.chloggen/1216.yaml deleted file mode 100644 index 27b98da42a..0000000000 --- a/.chloggen/1216.yaml +++ /dev/null @@ -1,5 +0,0 @@ -change_type: breaking -component: tls -note: > - Deprecate `tls.client.server_name attribute` in favor of common `server.address`. -issues: [ 1211, 1216 ] diff --git a/.chloggen/1239.yaml b/.chloggen/1239.yaml deleted file mode 100644 index 33a9ee75cb..0000000000 --- a/.chloggen/1239.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: network -note: Add QUIC to the list of well known network transports -issues: [ 1237, 1239 ] diff --git a/.chloggen/1241.yaml b/.chloggen/1241.yaml deleted file mode 100644 index a3af4264c3..0000000000 --- a/.chloggen/1241.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: breaking -component: messaging -note: Deprecate `messaging.destination_publish.*`` namespace and remove all usages. -issues: [ 1178, 1241 ] diff --git a/.chloggen/1243.yaml b/.chloggen/1243.yaml deleted file mode 100644 index 321a3dc7f4..0000000000 --- a/.chloggen/1243.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/1244.yaml b/.chloggen/1244.yaml deleted file mode 100644 index 849a02c9ff..0000000000 --- a/.chloggen/1244.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: db, messaging -note: Clarify that DB and messaging system-specific conventions override common ones -issues: [ 1235, 1244 ] diff --git a/.chloggen/1289.yaml b/.chloggen/1289.yaml deleted file mode 100644 index 2969b72017..0000000000 --- a/.chloggen/1289.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: db -note: Add better example of how to make the pool name unique -issues: [ 1289 ] diff --git a/.chloggen/1296.yaml b/.chloggen/1296.yaml deleted file mode 100644 index 8a1347f20a..0000000000 --- a/.chloggen/1296.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: docs -note: Update semantic conventions code generation documentation to use weaver instead of build-tools. -issues: [ 1296 ] diff --git a/.chloggen/1297.yaml b/.chloggen/1297.yaml deleted file mode 100644 index 3b907728a4..0000000000 --- a/.chloggen/1297.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: gen_ai -note: Add `server.address`, `server.port`, and `error.type` to GenAI spans. -issues: [ 1297 ] diff --git a/.chloggen/811.yaml b/.chloggen/811.yaml deleted file mode 100644 index dd2304d58b..0000000000 --- a/.chloggen/811.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: gen-ai -note: Adding metrics for GenAI clients. -issues: [811] diff --git a/.chloggen/815.yaml b/.chloggen/815.yaml deleted file mode 100644 index 202d2713f9..0000000000 --- a/.chloggen/815.yaml +++ /dev/null @@ -1,8 +0,0 @@ -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 ] diff --git a/.chloggen/839.yaml b/.chloggen/839.yaml deleted file mode 100644 index 1da8ca5ba8..0000000000 --- a/.chloggen/839.yaml +++ /dev/null @@ -1,4 +0,0 @@ -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] diff --git a/.chloggen/942.yaml b/.chloggen/942.yaml deleted file mode 100644 index d5920d949f..0000000000 --- a/.chloggen/942.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: messaging -note: Document `messaging.operation.name` for Azure messaging systems. -issues: [942] diff --git a/.chloggen/abbr.yaml b/.chloggen/abbr.yaml deleted file mode 100755 index 31b3df5e42..0000000000 --- a/.chloggen/abbr.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: all - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Define name abbreviations guidelines in attribute and metric names. - -# 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: [1121] - -# (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: diff --git a/.chloggen/add-azure-logs.yaml b/.chloggen/add-azure-logs.yaml deleted file mode 100644 index 2d14fa50a1..0000000000 --- a/.chloggen/add-azure-logs.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: azure - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add Azure SDK attributes & Logs event semantic conventions - -# 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: [1027] - -# (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: diff --git a/.chloggen/add-pulsar-message-system.yaml b/.chloggen/add-pulsar-message-system.yaml deleted file mode 100755 index d8853ac526..0000000000 --- a/.chloggen/add-pulsar-message-system.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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 pulsar message system - -# 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: [1099] - -# (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: diff --git a/.chloggen/add_linux_memory_slab.yaml b/.chloggen/add_linux_memory_slab.yaml deleted file mode 100755 index ebc232861f..0000000000 --- a/.chloggen/add_linux_memory_slab.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: linux - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add the `system.linux.memory.slab.usage` metric and the `linux.memory.slab.state` 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: [531] - -# (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: diff --git a/.chloggen/align_es_spec.yaml b/.chloggen/align_es_spec.yaml deleted file mode 100755 index 142eb7f6c9..0000000000 --- a/.chloggen/align_es_spec.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# 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: diff --git a/.chloggen/cicd-reg-attr.yaml b/.chloggen/cicd-reg-attr.yaml deleted file mode 100755 index a50fe72f31..0000000000 --- a/.chloggen/cicd-reg-attr.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# 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: cicd, deployment, artifact, test, vcs - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Adds CICD common attributes to the 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: [915, 832, 833] - -# (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: | - - CICD common attributes have been added to the registry. - - `deployment.environment` has been deprecated and moved to `deployment.environment.name`. diff --git a/.chloggen/cloud-events-restructure.yaml b/.chloggen/cloud-events-restructure.yaml deleted file mode 100755 index 90e15f3bc9..0000000000 --- a/.chloggen/cloud-events-restructure.yaml +++ /dev/null @@ -1,5 +0,0 @@ -change_type: 'enhancement' -component: cloudevents -note: CloudEvents conventions to follow HTTP/Messaging Span conventions -issues: [654] -subtext: diff --git a/.chloggen/database-batch-operations.yaml b/.chloggen/database-batch-operations.yaml deleted file mode 100644 index 30beccc95f..0000000000 --- a/.chloggen/database-batch-operations.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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 support for database batch operations - -# 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: [ 712 ] - -# (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: diff --git a/.chloggen/db_sanitization.yaml b/.chloggen/db_sanitization.yaml deleted file mode 100755 index a6d255ec26..0000000000 --- a/.chloggen/db_sanitization.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/extend-gen-ai-system-values.yaml b/.chloggen/extend-gen-ai-system-values.yaml deleted file mode 100755 index 619668e7d2..0000000000 --- a/.chloggen/extend-gen-ai-system-values.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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 3 well-known gen-ai systems as reference values of the gen-ai system 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: [ 1020 ] - -# (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: diff --git a/.chloggen/gcp-client-libraries.yaml b/.chloggen/gcp-client-libraries.yaml deleted file mode 100755 index 0ae23ba749..0000000000 --- a/.chloggen/gcp-client-libraries.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: 'enhancement' -component: gcp -note: Introduces `gcp.client.service` scope attribute. -issues: [ 1047 ] diff --git a/.chloggen/go-runtime-metrics.yaml b/.chloggen/go-runtime-metrics.yaml deleted file mode 100644 index 72e6aafe9a..0000000000 --- a/.chloggen/go-runtime-metrics.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: go - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add new go namespace for Go 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: [535] - -# (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: diff --git a/.chloggen/influxdb.yaml b/.chloggen/influxdb.yaml deleted file mode 100644 index ae6540b5ae..0000000000 --- a/.chloggen/influxdb.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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 semantic convention of InfluxDB - -# 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: [949] - -# (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: diff --git a/.chloggen/jvm_memory-buffer_metric_renaming.yaml b/.chloggen/jvm_memory-buffer_metric_renaming.yaml deleted file mode 100755 index 19ef16c697..0000000000 --- a/.chloggen/jvm_memory-buffer_metric_renaming.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: jvm - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: "Rename JVM metric `jvm.buffer.memory.usage` to `jvm.buffer.memory.used`" - -# 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: [288] - -# (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: diff --git a/.chloggen/log-original-body.yaml b/.chloggen/log-original-body.yaml deleted file mode 100755 index 858bf4242e..0000000000 --- a/.chloggen/log-original-body.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/merge_cpu_states.yaml b/.chloggen/merge_cpu_states.yaml deleted file mode 100755 index 54ea54c032..0000000000 --- a/.chloggen/merge_cpu_states.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: diff --git a/.chloggen/nodejs-metrics.yaml b/.chloggen/nodejs-metrics.yaml deleted file mode 100755 index 51b11a961e..0000000000 --- a/.chloggen/nodejs-metrics.yaml +++ /dev/null @@ -1,17 +0,0 @@ -# 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] diff --git a/.chloggen/session_start_end_event.yaml b/.chloggen/session_start_end_event.yaml deleted file mode 100755 index 1dd2bf020d..0000000000 --- a/.chloggen/session_start_end_event.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: 'session' - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add new experimental `session.start` and `session.end` events - -# 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: [1091] - -# (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: diff --git a/.chloggen/user_ns.yaml b/.chloggen/user_ns.yaml deleted file mode 100755 index 878e93a435..0000000000 --- a/.chloggen/user_ns.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# 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: user - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: BREAKING - deprecate `enduser` in favor of a new `user` namespace. Add more `user` 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: [731] - -# (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: diff --git a/.chloggen/v8js-metrics.yaml b/.chloggen/v8js-metrics.yaml deleted file mode 100644 index 276a49d500..0000000000 --- a/.chloggen/v8js-metrics.yaml +++ /dev/null @@ -1,17 +0,0 @@ -# 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] diff --git a/CHANGELOG.md b/CHANGELOG.md index dd3b88f886..6aae34d1d4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,90 @@ +## 1.27.0 + +### 🛑 Breaking changes 🛑 + +- `messaging`: 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` + (#1006, #947, #937) + +- `db`: 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. + (#1110) + +- `db`: Rename `db.client.connections.*` attributes to `db.client.connection.*` (#1125) +- `messaging`: Rename `messaging.kafka.message.offset` to `messaging.kafka.offset` (#1156) +- `db`: Sampling relevant attributes defined for database client spans (#1019) +- `tls`: Deprecate `tls.client.server_name attribute` in favor of common `server.address`. + (#1211, #1216) +- `messaging`: Deprecate `messaging.destination_publish.*`` namespace and remove all usages. (#1178, #1241) +- `messaging`: 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. + (#815) +- `db`: Align Elasticsearch span name to the general database span name guidelines. Deprecates `db.elasticsearch.cluster.name` in favor of `db.namespace`. + (#1002) +- `cicd, deployment, artifact, test, vcs`: Adds CICD common attributes to the registry. (#915, #832, #833) + - CICD common attributes have been added to the registry. + - `deployment.environment` has been deprecated and moved to `deployment.environment.name`. + +- `jvm`: Rename JVM metric `jvm.buffer.memory.usage` to `jvm.buffer.memory.used` (#288) +- `system`: Rename `process.cpu.state`, `container.cpu.state`, and `system.cpu.state` attributes into a common `cpu.mode` attribute (#840) + +### 🚀 New components 🚀 + +- `azure`: Add Azure SDK attributes & Logs event semantic conventions (#1027) +- `go`: Add new go namespace for Go runtime metrics (#535) +- `nodejs`: Introducing semantic conventions for Node.js runtime metrics. (#990) +- `user`: BREAKING - deprecate `enduser` in favor of a new `user` namespace. Add more `user` attributes. (#731) +- `v8js`: Introducing semantic conventions for V8 JS Engine runtime metrics. (#990) + +### 💡 Enhancements 💡 + +- `db`: List SQL database systems on the SQL semantic conventions. (#1024) +- `db`: Update database span name: clarify that target depends on the operation and should not be set when corresponding data is not available. (#1045) +- `db`: Mention how to capture collection and operation names from query text in the registry (#1070) +- `docs`: Don't render deprecated enum members in semconv tables. (#1110) +- `gen-ai`: Use GenAI instead of LLM on GenAI trace semantic conventions and minor cleanups. (#1087) +- `gen-ai`: Add GenAI model server metrics for measuring LLM serving latency (#1102) +- `db`: Clarify that `db.query.parameter.` is string representation of the parameter value (#1165) +- `messaging`: Clarify how per-message attributes should be recorded for batch operations. (#1168) +- `messaging`: Define sampling relevant attributes for messaging client spans (#432, #1169) +- `gen_ai`: 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. + (#1200) +- `gen_ai`: Convert `gen_ai.operation.name` to enum and use it on spans (#1202) +- `network`: Add QUIC to the list of well known network transports (#1237, #1239) +- `db`: `db.query.text` IN-clauses MAY be collapsed during the sanitization process (#1053) +- `db`, `messaging`: Clarify that DB and messaging system-specific conventions override common ones (#1235, #1244) +- `db`: Add better example of how to make the pool name unique (#1289) +- `docs`: Update semantic conventions code generation documentation to use weaver instead of build-tools. (#1296) +- `gen_ai`: Add `server.address`, `server.port`, and `error.type` to GenAI spans. (#1297) +- `gen-ai`: Adding metrics for GenAI clients. (#811) +- `gen-ai`: Adding `gen_ai.request.top_k`, `gen_ai.request.presence_penalty`, `gen_ai.request.frequency_penalty` and `gen_ai.request.stop_sequences` attributes. (#839) +- `messaging`: Document `messaging.operation.name` for Azure messaging systems. (#942) +- `all`: Define name abbreviations guidelines in attribute and metric names. (#1121) +- `messaging`: Add pulsar message system (#1099) +- `linux`: Add the `system.linux.memory.slab.usage` metric and the `linux.memory.slab.state` attributes. (#531) +- `cloudevents`: CloudEvents conventions to follow HTTP/Messaging Span conventions (#654) +- `db`: Add support for database batch operations (#712) +- `db`: Specify sanitization for `db.query.text`. (#717) +- `gen-ai`: Add 3 well-known gen-ai systems as reference values of the gen-ai system attribute (#1020) +- `gcp`: Introduces `gcp.client.service` scope attribute. (#1047) +- `db`: Add semantic convention of InfluxDB (#949) +- `log`: Add 'log.record.original' attribute. (#1137) +- `session`: Add new experimental `session.start` and `session.end` events (#1091) + +### 🧰 Bug fixes 🧰 + +- `messaging`: Update Kafka Spring example to align with the messaging spec (#1155) +- `http`: Relax requirement on when to set HTTP span status to Error from `MUST` to `SHOULD`. (#1167, #1003) + ## v1.26.0 ### 🛑 Breaking changes 🛑 diff --git a/schema-next.yaml b/schema-next.yaml index f475f28047..f16863d7df 100644 --- a/schema-next.yaml +++ b/schema-next.yaml @@ -2,12 +2,13 @@ file_format: 1.1.0 schema_url: https://opentelemetry.io/schemas/next versions: next: + 1.27.0: all: changes: # https://github.com/open-telemetry/semantic-conventions/pull/1216 - rename_attributes: - attribute_map: - tls.client.server_name: server.address + attribute_map: + tls.client.server_name: server.address # https://github.com/open-telemetry/semantic-conventions/pull/1075 - rename_attributes: attribute_map: diff --git a/schemas/1.27.0 b/schemas/1.27.0 new file mode 100644 index 0000000000..00cce6bc26 --- /dev/null +++ b/schemas/1.27.0 @@ -0,0 +1,505 @@ +file_format: 1.1.0 +schema_url: https://opentelemetry.io/schemas/1.27.0 +versions: + 1.27.0: + all: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1216 + - rename_attributes: + attribute_map: + tls.client.server_name: server.address + # https://github.com/open-telemetry/semantic-conventions/pull/1075 + - rename_attributes: + attribute_map: + deployment.environment: deployment.environment.name + # https://github.com/open-telemetry/semantic-conventions/pull/1245 + - rename_attributes: + attribute_map: + messaging.kafka.message.offset: messaging.kafka.offset + # https://github.com/open-telemetry/semantic-conventions/pull/815 + - rename_attributes: + attribute_map: + messaging.kafka.consumer.group: messaging.consumer.group.name + messaging.rocketmq.client_group: messaging.consumer.group.name + messaging.evenhubs.consumer.group: messaging.consumer.group.name + message.servicebus.destination.subscription_name: messaging.destination.subscription.name + # https://github.com/open-telemetry/semantic-conventions/pull/1200 + - rename_attributes: + attribute_map: + gen_ai.usage.completion_tokens: gen_ai.usage.output_tokens + gen_ai.usage.prompt_tokens: gen_ai.usage.input_tokens + spans: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1002 + - rename_attributes: + attribute_map: + db.elasticsearch.cluster.name: db.namespace + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1125 + - rename_attributes: + attribute_map: + db.client.connections.state: db.client.connection.state + apply_to_metrics: + - db.client.connection.count + - rename_attributes: + attribute_map: + db.client.connections.pool.name: db.client.connection.pool.name + apply_to_metrics: + - db.client.connection.count + - db.client.connection.idle.max + - db.client.connection.idle.min + - db.client.connection.max + - db.client.connection.pending_requests + - db.client.connection.timeouts + - db.client.connection.create_time + - db.client.connection.wait_time + - db.client.connection.use_time + # https://github.com/open-telemetry/semantic-conventions/pull/1006 + - rename_metrics: + messaging.publish.messages: messaging.client.published.messages + # https://github.com/open-telemetry/semantic-conventions/pull/1026 + - rename_attributes: + attribute_map: + system.cpu.state: cpu.mode + process.cpu.state: cpu.mode + container.cpu.state: cpu.mode + apply_to_metrics: + - system.cpu.time + - system.cpu.utilization + - process.cpu.time + - process.cpu.utilization + - container.cpu.time + # https://github.com/open-telemetry/semantic-conventions/pull/1265 + - rename_metrics: + jvm.buffer.memory.usage: jvm.buffer.memory.used + 1.26.0: + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/966 + - rename_metrics: + db.client.connections.usage: db.client.connection.count + db.client.connections.idle.max: db.client.connection.idle.max + db.client.connections.idle.min: db.client.connection.idle.min + db.client.connections.max: db.client.connection.max + db.client.connections.pending_requests: db.client.connection.pending_requests + db.client.connections.timeouts: db.client.connection.timeouts + # https://github.com/open-telemetry/semantic-conventions/pull/948 + - rename_attributes: + attribute_map: + messaging.client_id: messaging.client.id + # https://github.com/open-telemetry/semantic-conventions/pull/909 + - rename_attributes: + attribute_map: + state: db.client.connections.state + apply_to_metrics: + - db.client.connections.usage + - rename_attributes: + attribute_map: + pool.name: db.client.connections.pool.name + apply_to_metrics: + - db.client.connections.usage + - db.client.connections.idle.max + - db.client.connections.idle.min + - db.client.connections.max + - db.client.connections.pending_requests + - db.client.connections.timeouts + - db.client.connections.create_time + - db.client.connections.wait_time + - db.client.connections.use_time + all: + changes: + # https://github:com/open-telemetry/semantic-conventions/pull/731/ + - rename_attributes: + attribute_map: + enduser.id: user.id + + 1.25.0: + spans: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/911 + - rename_attributes: + attribute_map: + db.name: db.namespace + # https://github.com/open-telemetry/semantic-conventions/pull/870 + - rename_attributes: + attribute_map: + db.sql.table: db.collection.name + db.mongodb.collection: db.collection.name + db.cosmosdb.container: db.collection.name + db.cassandra.table: db.collection.name + # https://github.com/open-telemetry/semantic-conventions/pull/798 + - rename_attributes: + attribute_map: + messaging.kafka.destination.partition: messaging.destination.partition.id + # https://github.com/open-telemetry/semantic-conventions/pull/875 + - rename_attributes: + attribute_map: + db.operation: db.operation.name + # https://github.com/open-telemetry/semantic-conventions/pull/913 + - rename_attributes: + attribute_map: + messaging.operation: messaging.operation.type + # https://github.com/open-telemetry/semantic-conventions/pull/866 + - rename_attributes: + attribute_map: + db.statement: db.query.text + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/484 + - rename_attributes: + attribute_map: + system.processes.status: system.process.status + apply_to_metrics: + - system.processes.count + - rename_metrics: + system.processes.count: system.process.count + system.processes.created: system.process.created + # https://github.com/open-telemetry/semantic-conventions/pull/625 + - rename_attributes: + attribute_map: + container.labels: container.label + k8s.pod.labels: k8s.pod.label + # https://github.com/open-telemetry/semantic-conventions/pull/330 + - rename_metrics: + process.threads: process.thread.count + process.open_file_descriptors: process.open_file_descriptor.count + - rename_attributes: + attribute_map: + state: process.cpu.state + apply_to_metrics: + - process.cpu.time + - process.cpu.utilization + - rename_attributes: + attribute_map: + direction: disk.io.direction + apply_to_metrics: + - process.disk.io + - rename_attributes: + attribute_map: + type: process.context_switch_type + apply_to_metrics: + - process.context_switches + - rename_attributes: + attribute_map: + direction: network.io.direction + apply_to_metrics: + - process.network.io + - rename_attributes: + attribute_map: + type: process.paging.fault_type + apply_to_metrics: + - process.paging.faults + all: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/854 + - rename_attributes: + attribute_map: + message.type: rpc.message.type + message.id: rpc.message.id + message.compressed_size: rpc.message.compressed_size + message.uncompressed_size: rpc.message.uncompressed_size + + 1.24.0: + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/536 + - rename_metrics: + jvm.memory.usage: jvm.memory.used + jvm.memory.usage_after_last_gc: jvm.memory.used_after_last_gc + # https://github.com/open-telemetry/semantic-conventions/pull/530 + - rename_attributes: + attribute_map: + system.network.io.direction: network.io.direction + system.disk.io.direction: disk.io.direction + 1.23.1: + 1.23.0: + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/20 + - rename_attributes: + attribute_map: + thread.daemon: jvm.thread.daemon + apply_to_metrics: + - jvm.thread.count + 1.22.0: + spans: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/229 + - rename_attributes: + attribute_map: + messaging.message.payload_size_bytes: messaging.message.body.size + # https://github.com/open-telemetry/opentelemetry-specification/pull/374 + - rename_attributes: + attribute_map: + http.resend_count: http.request.resend_count + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/224 + - rename_metrics: + http.client.duration: http.client.request.duration + http.server.duration: http.server.request.duration + # https://github.com/open-telemetry/semantic-conventions/pull/241 + - rename_metrics: + process.runtime.jvm.memory.usage: jvm.memory.usage + process.runtime.jvm.memory.committed: jvm.memory.committed + process.runtime.jvm.memory.limit: jvm.memory.limit + process.runtime.jvm.memory.usage_after_last_gc: jvm.memory.usage_after_last_gc + process.runtime.jvm.gc.duration: jvm.gc.duration + # also https://github.com/open-telemetry/semantic-conventions/pull/252 + process.runtime.jvm.threads.count: jvm.thread.count + # also https://github.com/open-telemetry/semantic-conventions/pull/252 + process.runtime.jvm.classes.loaded: jvm.class.loaded + # also https://github.com/open-telemetry/semantic-conventions/pull/252 + process.runtime.jvm.classes.unloaded: jvm.class.unloaded + # also https://github.com/open-telemetry/semantic-conventions/pull/252 + # and https://github.com/open-telemetry/semantic-conventions/pull/60 + process.runtime.jvm.classes.current_loaded: jvm.class.count + process.runtime.jvm.cpu.time: jvm.cpu.time + process.runtime.jvm.cpu.recent_utilization: jvm.cpu.recent_utilization + process.runtime.jvm.memory.init: jvm.memory.init + process.runtime.jvm.system.cpu.utilization: jvm.system.cpu.utilization + process.runtime.jvm.system.cpu.load_1m: jvm.system.cpu.load_1m + # https://github.com/open-telemetry/semantic-conventions/pull/253 + process.runtime.jvm.buffer.usage: jvm.buffer.memory.usage + # https://github.com/open-telemetry/semantic-conventions/pull/253 + process.runtime.jvm.buffer.limit: jvm.buffer.memory.limit + process.runtime.jvm.buffer.count: jvm.buffer.count + # https://github.com/open-telemetry/semantic-conventions/pull/20 + - rename_attributes: + attribute_map: + type: jvm.memory.type + pool: jvm.memory.pool.name + apply_to_metrics: + - jvm.memory.usage + - jvm.memory.committed + - jvm.memory.limit + - jvm.memory.usage_after_last_gc + - jvm.memory.init + - rename_attributes: + attribute_map: + name: jvm.gc.name + action: jvm.gc.action + apply_to_metrics: + - jvm.gc.duration + - rename_attributes: + attribute_map: + daemon: thread.daemon + apply_to_metrics: + - jvm.threads.count + - rename_attributes: + attribute_map: + pool: jvm.buffer.pool.name + apply_to_metrics: + - jvm.buffer.memory.usage + - jvm.buffer.memory.limit + - jvm.buffer.count + # https://github.com/open-telemetry/semantic-conventions/pull/89 + - rename_attributes: + attribute_map: + state: system.cpu.state + cpu: system.cpu.logical_number + apply_to_metrics: + - system.cpu.time + - system.cpu.utilization + - rename_attributes: + attribute_map: + state: system.memory.state + apply_to_metrics: + - system.memory.usage + - system.memory.utilization + - rename_attributes: + attribute_map: + state: system.paging.state + apply_to_metrics: + - system.paging.usage + - system.paging.utilization + - rename_attributes: + attribute_map: + type: system.paging.type + direction: system.paging.direction + apply_to_metrics: + - system.paging.faults + - system.paging.operations + - rename_attributes: + attribute_map: + device: system.device + direction: system.disk.direction + apply_to_metrics: + - system.disk.io + - system.disk.operations + - system.disk.io_time + - system.disk.operation_time + - system.disk.merged + - rename_attributes: + attribute_map: + device: system.device + state: system.filesystem.state + type: system.filesystem.type + mode: system.filesystem.mode + mountpoint: system.filesystem.mountpoint + apply_to_metrics: + - system.filesystem.usage + - system.filesystem.utilization + - rename_attributes: + attribute_map: + device: system.device + direction: system.network.direction + protocol: network.protocol + state: system.network.state + apply_to_metrics: + - system.network.dropped + - system.network.packets + - system.network.errors + - system.network.io + - system.network.connections + - rename_attributes: + attribute_map: + status: system.processes.status + apply_to_metrics: + - system.processes.count + # https://github.com/open-telemetry/semantic-conventions/pull/247 + - rename_metrics: + http.server.request.size: http.server.request.body.size + http.server.response.size: http.server.response.body.size + resources: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/178 + - rename_attributes: + attribute_map: + telemetry.auto.version: telemetry.distro.version + 1.21.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/3336 + - rename_attributes: + attribute_map: + messaging.kafka.client_id: messaging.client_id + messaging.rocketmq.client_id: messaging.client_id + # https://github.com/open-telemetry/opentelemetry-specification/pull/3402 + - rename_attributes: + attribute_map: + # net.peer.(name|port) attributes were usually populated on client side + # so they should be usually translated to server.(address|port) + # net.host.* attributes were only populated on server side + net.host.name: server.address + net.host.port: server.port + # was only populated on client side + net.sock.peer.name: server.socket.domain + # net.sock.peer.(addr|port) mapping is not possible + # since they applied to both client and server side + # were only populated on server side + net.sock.host.addr: server.socket.address + net.sock.host.port: server.socket.port + http.client_ip: client.address + # https://github.com/open-telemetry/opentelemetry-specification/pull/3426 + - rename_attributes: + attribute_map: + net.protocol.name: network.protocol.name + net.protocol.version: network.protocol.version + net.host.connection.type: network.connection.type + net.host.connection.subtype: network.connection.subtype + net.host.carrier.name: network.carrier.name + net.host.carrier.mcc: network.carrier.mcc + net.host.carrier.mnc: network.carrier.mnc + net.host.carrier.icc: network.carrier.icc + # https://github.com/open-telemetry/opentelemetry-specification/pull/3355 + - rename_attributes: + attribute_map: + http.method: http.request.method + http.status_code: http.response.status_code + http.scheme: url.scheme + http.url: url.full + http.request_content_length: http.request.body.size + http.response_content_length: http.response.body.size + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/53 + - rename_metrics: + process.runtime.jvm.cpu.utilization: process.runtime.jvm.cpu.recent_utilization + 1.20.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/3272 + - rename_attributes: + attribute_map: + net.app.protocol.name: net.protocol.name + net.app.protocol.version: net.protocol.version + 1.19.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/3209 + - rename_attributes: + attribute_map: + faas.execution: faas.invocation_id + # https://github.com/open-telemetry/opentelemetry-specification/pull/3188 + - rename_attributes: + attribute_map: + faas.id: cloud.resource_id + # https://github.com/open-telemetry/opentelemetry-specification/pull/3190 + - rename_attributes: + attribute_map: + http.user_agent: user_agent.original + resources: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/3190 + - rename_attributes: + attribute_map: + browser.user_agent: user_agent.original + 1.18.0: + 1.17.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/2957 + - rename_attributes: + attribute_map: + messaging.consumer_id: messaging.consumer.id + messaging.protocol: net.app.protocol.name + messaging.protocol_version: net.app.protocol.version + messaging.destination: messaging.destination.name + messaging.temp_destination: messaging.destination.temporary + messaging.destination_kind: messaging.destination.kind + messaging.message_id: messaging.message.id + messaging.conversation_id: messaging.message.conversation_id + messaging.message_payload_size_bytes: messaging.message.payload_size_bytes + messaging.message_payload_compressed_size_bytes: messaging.message.payload_compressed_size_bytes + messaging.rabbitmq.routing_key: messaging.rabbitmq.destination.routing_key + messaging.kafka.message_key: messaging.kafka.message.key + messaging.kafka.partition: messaging.kafka.destination.partition + messaging.kafka.tombstone: messaging.kafka.message.tombstone + messaging.rocketmq.message_type: messaging.rocketmq.message.type + messaging.rocketmq.message_tag: messaging.rocketmq.message.tag + messaging.rocketmq.message_keys: messaging.rocketmq.message.keys + messaging.kafka.consumer_group: messaging.kafka.consumer.group + 1.16.0: + 1.15.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/2743 + - rename_attributes: + attribute_map: + http.retry_count: http.resend_count + 1.14.0: + 1.13.0: + spans: + changes: + # https://github.com/open-telemetry/opentelemetry-specification/pull/2614 + - rename_attributes: + attribute_map: + net.peer.ip: net.sock.peer.addr + net.host.ip: net.sock.host.addr + 1.12.0: + 1.11.0: + 1.10.0: + 1.9.0: + 1.8.0: + spans: + changes: + - rename_attributes: + attribute_map: + db.cassandra.keyspace: db.name + db.hbase.namespace: db.name + 1.7.0: + 1.6.1: + 1.5.0: + 1.4.0: