From ac424df0d09fae721913f2a399b90ac16ba960fd Mon Sep 17 00:00:00 2001 From: OpenTelemetry Bot <107717825+opentelemetrybot@users.noreply.github.com> Date: Fri, 24 Jan 2025 11:04:57 -0800 Subject: [PATCH] Prepare release v1.30.0 (#1809) Co-authored-by: Trask Stalnaker --- .chloggen/.oracle_cloud.yaml | 22 - .chloggen/1469.yaml | 5 - .chloggen/1600-cicd-metrics.yaml | 27 - .chloggen/1646.yaml | 4 - .chloggen/1655.yaml | 24 - .chloggen/1694.yaml | 8 - .chloggen/1715.yaml | 22 - .chloggen/1716.yaml | 4 - .chloggen/1719.yaml | 22 - .chloggen/1734.yaml | 12 - .chloggen/1772.yaml | 22 - .chloggen/1779.yaml | 4 - .chloggen/add_deploy_replica_metrics.yaml | 25 - .chloggen/add_ds_metrics.yaml | 22 - .chloggen/add_k8s_jobs.yaml | 22 - .chloggen/add_k8s_ns_phase.yaml | 22 - .chloggen/aws.extended_request_id.yaml | 22 - .chloggen/clarify-temporary-destination.yaml | 5 - .chloggen/code-rename.yaml | 26 - .chloggen/fix_system_net_state.yaml | 22 - .chloggen/genai-request-seed.yaml | 5 - .chloggen/improve_cpu_brief.yaml | 22 - .chloggen/k8s-migration.yaml | 22 - .chloggen/profile-frame-type-beam.yaml | 22 - .chloggen/rabbitmq-destination-name.yaml | 4 - .chloggen/rule_new.yaml | 22 - .chloggen/stable-dotnet-runtime-metrics.yaml | 22 - .chloggen/vcs-1254.yaml | 25 - .chloggen/vcs-ttm.yaml | 22 - CHANGELOG.md | 66 +++ schema-next.yaml | 5 +- schemas/1.30.0 | 580 +++++++++++++++++++ 32 files changed, 650 insertions(+), 509 deletions(-) delete mode 100644 .chloggen/.oracle_cloud.yaml delete mode 100644 .chloggen/1469.yaml delete mode 100644 .chloggen/1600-cicd-metrics.yaml delete mode 100644 .chloggen/1646.yaml delete mode 100644 .chloggen/1655.yaml delete mode 100644 .chloggen/1694.yaml delete mode 100644 .chloggen/1715.yaml delete mode 100644 .chloggen/1716.yaml delete mode 100644 .chloggen/1719.yaml delete mode 100644 .chloggen/1734.yaml delete mode 100644 .chloggen/1772.yaml delete mode 100644 .chloggen/1779.yaml delete mode 100755 .chloggen/add_deploy_replica_metrics.yaml delete mode 100755 .chloggen/add_ds_metrics.yaml delete mode 100755 .chloggen/add_k8s_jobs.yaml delete mode 100755 .chloggen/add_k8s_ns_phase.yaml delete mode 100644 .chloggen/aws.extended_request_id.yaml delete mode 100644 .chloggen/clarify-temporary-destination.yaml delete mode 100644 .chloggen/code-rename.yaml delete mode 100755 .chloggen/fix_system_net_state.yaml delete mode 100644 .chloggen/genai-request-seed.yaml delete mode 100755 .chloggen/improve_cpu_brief.yaml delete mode 100755 .chloggen/k8s-migration.yaml delete mode 100755 .chloggen/profile-frame-type-beam.yaml delete mode 100755 .chloggen/rabbitmq-destination-name.yaml delete mode 100755 .chloggen/rule_new.yaml delete mode 100644 .chloggen/stable-dotnet-runtime-metrics.yaml delete mode 100755 .chloggen/vcs-1254.yaml delete mode 100755 .chloggen/vcs-ttm.yaml create mode 100644 schemas/1.30.0 diff --git a/.chloggen/.oracle_cloud.yaml b/.chloggen/.oracle_cloud.yaml deleted file mode 100644 index fb402ce405..0000000000 --- a/.chloggen/.oracle_cloud.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: cloud - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add Oracle Cloud Infrastructure to 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: [1658] - -# (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/1469.yaml b/.chloggen/1469.yaml deleted file mode 100644 index 7d7b4ba5cc..0000000000 --- a/.chloggen/1469.yaml +++ /dev/null @@ -1,5 +0,0 @@ -change_type: 'enhancement' -component: gen_ai -note: Yamlify gen_ai events and clean up examples. - -issues: [1469] diff --git a/.chloggen/1600-cicd-metrics.yaml b/.chloggen/1600-cicd-metrics.yaml deleted file mode 100644 index fe134b1f5b..0000000000 --- a/.chloggen/1600-cicd-metrics.yaml +++ /dev/null @@ -1,27 +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: cicd - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add CICD 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: [1600] - -# (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: | - Makes the following changes: - - - Add metrics `cicd.pipeline.run.duration`, `cicd.pipeline.run.active`, `cicd.worker.count`, - `cicd.pipeline.run.errors` and `cicd.system.errors`. - - The CICD attributes `cicd.pipeline.run.state`, `cicd.pipeline.result`, `cicd.system.component`, `cicd.worker.state` have been added to the registry. diff --git a/.chloggen/1646.yaml b/.chloggen/1646.yaml deleted file mode 100644 index 778acd9c9a..0000000000 --- a/.chloggen/1646.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: breaking -component: event -note: Deprecate `event.name` attribute in favor of the top level event name property on the log record -issues: [1646] diff --git a/.chloggen/1655.yaml b/.chloggen/1655.yaml deleted file mode 100644 index d833884e93..0000000000 --- a/.chloggen/1655.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: 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: | - Adds OpenAI API compatible `gen_ai.system` attribute values: `az.ai.openai`, `deepseek`, `gemini`, `groq`, - `perplexity` and `xai`. Elaborates that `openai` can be ambiguous due to API emulation. - -# 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: [1655] - -# (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/1694.yaml b/.chloggen/1694.yaml deleted file mode 100644 index ddf40d60a4..0000000000 --- a/.chloggen/1694.yaml +++ /dev/null @@ -1,8 +0,0 @@ -change_type: enhancement -component: docs -note: Update attribute, events, and metrics naming guidance to include new best practices. -subtext: | - - Use namespaces (with `.` delimiter) whenever possible. - - Use precise, descriptive, unambiguous names that leave room for expansion. - -issues: [1694] diff --git a/.chloggen/1715.yaml b/.chloggen/1715.yaml deleted file mode 100644 index 677bad9615..0000000000 --- a/.chloggen/1715.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: gen_ai - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Rename `gen_ai.openai.request.seed` to `gen_ai.request.seed` and use it on general GenAI 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: [1715] - -# (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/1716.yaml b/.chloggen/1716.yaml deleted file mode 100644 index 1c16bf56d1..0000000000 --- a/.chloggen/1716.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: docs, db -note: Add common guidance for recording errors on spans and metrics, clarify DB conventions. -issues: [1516, 1536, 1716] diff --git a/.chloggen/1719.yaml b/.chloggen/1719.yaml deleted file mode 100644 index 74ed83fd35..0000000000 --- a/.chloggen/1719.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: Adds `mistral_ai` as a `gen_ai.system` attribute 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: [1719] - -# (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/1734.yaml b/.chloggen/1734.yaml deleted file mode 100644 index 5e9cb2eaa1..0000000000 --- a/.chloggen/1734.yaml +++ /dev/null @@ -1,12 +0,0 @@ -change_type: breaking - -component: db - -note: | - Rename `db.system` to `db.system.name` and clean up its values. - Rename `db.elasticsearch.*`, `db.cassandra.*`, `db.cosmosdb.*` attributes to `elasticsearch.*`, `cassandra.*`, and `azure.cosmosdb.*` respectively. - Rename `db.client.cosmosdb.*` metrics to `azure.cosmosdb.client.*`. - -issues: [1581, 608] - -subtext: diff --git a/.chloggen/1772.yaml b/.chloggen/1772.yaml deleted file mode 100644 index 255b75cc8a..0000000000 --- a/.chloggen/1772.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: process - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Update `process.runtime` example for the Python language. - -# 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: [1772] - -# (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/1779.yaml b/.chloggen/1779.yaml deleted file mode 100644 index 8773a209c4..0000000000 --- a/.chloggen/1779.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: enhancement -component: db -note: Add metrics section to each of the database system-specific conventions. -issues: [1447, 1779] diff --git a/.chloggen/add_deploy_replica_metrics.yaml b/.chloggen/add_deploy_replica_metrics.yaml deleted file mode 100755 index 09a9bea9c8..0000000000 --- a/.chloggen/add_deploy_replica_metrics.yaml +++ /dev/null @@ -1,25 +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: k8s - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add metrics for k8s deployment, replicaset, replication_controller, statefulset and hpa. - -# 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: [1636, 1637, 1644] - -# (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: | - This addition focused on providing consistency between these metrics, while - also ensuring alignment with recommendations from Kubernetes. - More details in https://github.com/open-telemetry/semantic-conventions/issues/1637 diff --git a/.chloggen/add_ds_metrics.yaml b/.chloggen/add_ds_metrics.yaml deleted file mode 100755 index d8a68d2311..0000000000 --- a/.chloggen/add_ds_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: enhancement - -# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db) -component: k8s - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add k8s deamonset related 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: [1649] - -# (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_k8s_jobs.yaml b/.chloggen/add_k8s_jobs.yaml deleted file mode 100755 index 1937c814f5..0000000000 --- a/.chloggen/add_k8s_jobs.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: k8s - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add k8s metrics for job and cronjob - -# 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: [1660] - -# (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_k8s_ns_phase.yaml b/.chloggen/add_k8s_ns_phase.yaml deleted file mode 100755 index b7813687e3..0000000000 --- a/.chloggen/add_k8s_ns_phase.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: k8s - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add k8s.namespace.phase metric along with the respective 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: [1668] - -# (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/aws.extended_request_id.yaml b/.chloggen/aws.extended_request_id.yaml deleted file mode 100644 index 3b0e7bd0f5..0000000000 --- a/.chloggen/aws.extended_request_id.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: aws - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add extended request ID to general AWS attributes as `aws.extended_request_id` - -# 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: [1670] - -# (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/clarify-temporary-destination.yaml b/.chloggen/clarify-temporary-destination.yaml deleted file mode 100644 index fb6d9e52b9..0000000000 --- a/.chloggen/clarify-temporary-destination.yaml +++ /dev/null @@ -1,5 +0,0 @@ -change_type: enhancement -component: messaging -note: Further clarify `{destination}` value on span names -issues: [1635] -subtext: diff --git a/.chloggen/code-rename.yaml b/.chloggen/code-rename.yaml deleted file mode 100644 index a6192f3d12..0000000000 --- a/.chloggen/code-rename.yaml +++ /dev/null @@ -1,26 +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: code - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: rename `code.function`, `code.lineno`, `code.column` and `code.filepath` - -# 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: [ 1377, 1599 ] - -# (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: | - `code.function` renamed to `code.function.name` - `code.lineno` renamed to `code.line.number` - `code.column` renamed to `code.column.number` - `code.filepath` renamed to `code.file.path` diff --git a/.chloggen/fix_system_net_state.yaml b/.chloggen/fix_system_net_state.yaml deleted file mode 100755 index 0176d27b51..0000000000 --- a/.chloggen/fix_system_net_state.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: Replace `system.network.state` with `network.connection.state` - -# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. -# The values here must be integers. -issues: [308] - -# (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/genai-request-seed.yaml b/.chloggen/genai-request-seed.yaml deleted file mode 100644 index 0c19365120..0000000000 --- a/.chloggen/genai-request-seed.yaml +++ /dev/null @@ -1,5 +0,0 @@ -change_type: 'enhancement' -component: gen_ai -note: Introduce gen_ai.request.seed and deprecated gen_ai.openai.request.seed - -issues: [1710] diff --git a/.chloggen/improve_cpu_brief.yaml b/.chloggen/improve_cpu_brief.yaml deleted file mode 100755 index 4642419f39..0000000000 --- a/.chloggen/improve_cpu_brief.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: system - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Adds note about how `system.cpu.physical.count` and `system.cpu.logical.count` are calculated - -# 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: [1780] - -# (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/k8s-migration.yaml b/.chloggen/k8s-migration.yaml deleted file mode 100755 index f9a4de7bbe..0000000000 --- a/.chloggen/k8s-migration.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: k8s - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add migration guide for K8s 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: [1597] - -# (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/profile-frame-type-beam.yaml b/.chloggen/profile-frame-type-beam.yaml deleted file mode 100755 index ea16a6532b..0000000000 --- a/.chloggen/profile-frame-type-beam.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: profile - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: 'Extend the list of known frame types with a value for Erlang' - -# 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: [1735] - -# (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/rabbitmq-destination-name.yaml b/.chloggen/rabbitmq-destination-name.yaml deleted file mode 100755 index 2d795f1b44..0000000000 --- a/.chloggen/rabbitmq-destination-name.yaml +++ /dev/null @@ -1,4 +0,0 @@ -change_type: breaking -component: messaging -note: "RabbitMQ: Specify how to populate `messaging.destination.name`" -issues: [1529] diff --git a/.chloggen/rule_new.yaml b/.chloggen/rule_new.yaml deleted file mode 100755 index 35b29d4c95..0000000000 --- a/.chloggen/rule_new.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: security-rule - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Introducing a new security rule 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: [903] - -# (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/stable-dotnet-runtime-metrics.yaml b/.chloggen/stable-dotnet-runtime-metrics.yaml deleted file mode 100644 index ac6b3135ec..0000000000 --- a/.chloggen/stable-dotnet-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: enhancement - -# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db) -component: dotnet - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Mark .NET runtime metrics as stable - -# 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: [1602] - -# (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/vcs-1254.yaml b/.chloggen/vcs-1254.yaml deleted file mode 100755 index bbb88ac423..0000000000 --- a/.chloggen/vcs-1254.yaml +++ /dev/null @@ -1,25 +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: vcs - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: | - Adds `vcs.repository.name` attribute to registry and update - `vcs.repository.url.full` description for consistent representation. Updates - the VCS metrics to include `vcs.repository.name` as a recommended 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: [1254, 1453] - -# (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/vcs-ttm.yaml b/.chloggen/vcs-ttm.yaml deleted file mode 100755 index 25f2671a70..0000000000 --- a/.chloggen/vcs-ttm.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: vcs - -# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). -note: Add `vcs.change.time_to_merge` metric. - -# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. -# The values here must be integers. -issues: [1685] - -# (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/CHANGELOG.md b/CHANGELOG.md index e245552a74..2bf1a685e9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,72 @@ +## v1.30.0 + +### 🛑 Breaking changes 🛑 + +- `event`: Deprecate `event.name` attribute in favor of the top level event name property on the log record ([#1646](https://github.com/open-telemetry/semantic-conventions/issues/1646)) +- `gen_ai`: Rename `gen_ai.openai.request.seed` to `gen_ai.request.seed` and use it on general GenAI conventions. ([#1715](https://github.com/open-telemetry/semantic-conventions/issues/1715)) +- `db`: Rename `db.system` to `db.system.name` and clean up its values. +Rename `db.elasticsearch.*`, `db.cassandra.*`, `db.cosmosdb.*` attributes to `elasticsearch.*`, `cassandra.*`, and `azure.cosmosdb.*` respectively. +Rename `db.client.cosmosdb.*` metrics to `azure.cosmosdb.client.*`. + ([#1581](https://github.com/open-telemetry/semantic-conventions/issues/1581), [#608](https://github.com/open-telemetry/semantic-conventions/issues/608)) +- `code`: rename `code.function`, `code.lineno`, `code.column` and `code.filepath` ([#1377](https://github.com/open-telemetry/semantic-conventions/issues/1377), [#1599](https://github.com/open-telemetry/semantic-conventions/issues/1599)) + `code.function` renamed to `code.function.name` + `code.lineno` renamed to `code.line.number` + `code.column` renamed to `code.column.number` + `code.filepath` renamed to `code.file.path` + +- `system`: Replace `system.network.state` with `network.connection.state` ([#308](https://github.com/open-telemetry/semantic-conventions/issues/308)) +- `messaging`: RabbitMQ: Specify how to populate `messaging.destination.name` ([#1529](https://github.com/open-telemetry/semantic-conventions/issues/1529)) + +### 🚀 New components 🚀 + +- `security-rule`: Introducing a new security rule namespace ([#903](https://github.com/open-telemetry/semantic-conventions/issues/903)) + +### 💡 Enhancements 💡 + +- `cloud`: Add Oracle Cloud Infrastructure to Semantic Conventions ([#1658](https://github.com/open-telemetry/semantic-conventions/issues/1658)) +- `gen_ai`: Yamlify gen_ai events and clean up examples. ([#1469](https://github.com/open-telemetry/semantic-conventions/issues/1469)) +- `cicd`: Add CICD metrics ([#1600](https://github.com/open-telemetry/semantic-conventions/issues/1600)) + Makes the following changes: + + - Add metrics `cicd.pipeline.run.duration`, `cicd.pipeline.run.active`, `cicd.worker.count`, + `cicd.pipeline.run.errors` and `cicd.system.errors`. + - The CICD attributes `cicd.pipeline.run.state`, `cicd.pipeline.result`, `cicd.system.component`, `cicd.worker.state` have been added to the registry. + +- `gen-ai`: Adds OpenAI API compatible `gen_ai.system` attribute values: `az.ai.openai`, `deepseek`, `gemini`, `groq`, +`perplexity` and `xai`. Elaborates that `openai` can be ambiguous due to API emulation. + ([#1655](https://github.com/open-telemetry/semantic-conventions/issues/1655)) +- `docs`: Update attribute, events, and metrics naming guidance to include new best practices. ([#1694](https://github.com/open-telemetry/semantic-conventions/issues/1694)) + - Use namespaces (with `.` delimiter) whenever possible. + - Use precise, descriptive, unambiguous names that leave room for expansion. + +- `docs, db`: Add common guidance for recording errors on spans and metrics, clarify DB conventions. ([#1516](https://github.com/open-telemetry/semantic-conventions/issues/1516), [#1536](https://github.com/open-telemetry/semantic-conventions/issues/1536), [#1716](https://github.com/open-telemetry/semantic-conventions/issues/1716)) +- `gen-ai`: Adds `mistral_ai` as a `gen_ai.system` attribute value. ([#1719](https://github.com/open-telemetry/semantic-conventions/issues/1719)) +- `process`: Update `process.runtime` example for the Python language. ([#1772](https://github.com/open-telemetry/semantic-conventions/issues/1772)) +- `db`: Add metrics section to each of the database system-specific conventions. ([#1447](https://github.com/open-telemetry/semantic-conventions/issues/1447), [#1779](https://github.com/open-telemetry/semantic-conventions/issues/1779)) +- `k8s`: Add metrics for k8s deployment, replicaset, replication_controller, statefulset and hpa. ([#1636](https://github.com/open-telemetry/semantic-conventions/issues/1636), [#1637](https://github.com/open-telemetry/semantic-conventions/issues/1637), [#1644](https://github.com/open-telemetry/semantic-conventions/issues/1644)) + This addition focused on providing consistency between these metrics, while + also ensuring alignment with recommendations from Kubernetes. + More details in [#1637](https://github.com/open-telemetry/semantic-conventions/issues/1637) + +- `k8s`: Add k8s deamonset related metrics ([#1649](https://github.com/open-telemetry/semantic-conventions/issues/1649)) +- `k8s`: Add k8s metrics for job and cronjob ([#1660](https://github.com/open-telemetry/semantic-conventions/issues/1660)) +- `k8s`: Add k8s.namespace.phase metric along with the respective attribute ([#1668](https://github.com/open-telemetry/semantic-conventions/issues/1668)) +- `aws`: Add extended request ID to general AWS attributes as `aws.extended_request_id` ([#1670](https://github.com/open-telemetry/semantic-conventions/issues/1670)) +- `messaging`: Further clarify `{destination}` value on span names ([#1635](https://github.com/open-telemetry/semantic-conventions/issues/1635)) +- `gen_ai`: Introduce gen_ai.request.seed and deprecated gen_ai.openai.request.seed ([#1710](https://github.com/open-telemetry/semantic-conventions/issues/1710)) +- `system`: Adds note about how `system.cpu.physical.count` and `system.cpu.logical.count` are calculated ([#1780](https://github.com/open-telemetry/semantic-conventions/issues/1780)) +- `k8s`: Add migration guide for K8s semantic conventions ([#1597](https://github.com/open-telemetry/semantic-conventions/issues/1597)) +- `profile`: Extend the list of known frame types with a value for Erlang ([#1735](https://github.com/open-telemetry/semantic-conventions/issues/1735)) +- `dotnet`: Mark .NET runtime metrics as stable ([#1602](https://github.com/open-telemetry/semantic-conventions/issues/1602)) +- `vcs`: Adds `vcs.repository.name` attribute to registry and update +`vcs.repository.url.full` description for consistent representation. Updates +the VCS metrics to include `vcs.repository.name` as a recommended attribute. + ([#1254](https://github.com/open-telemetry/semantic-conventions/issues/1254), [#1453](https://github.com/open-telemetry/semantic-conventions/issues/1453)) +- `vcs`: Add `vcs.change.time_to_merge` metric. ([#1685](https://github.com/open-telemetry/semantic-conventions/issues/1685)) + ## v1.29.0 ### 🛑 Breaking changes 🛑 diff --git a/schema-next.yaml b/schema-next.yaml index c708565d5e..fff1f374ef 100644 --- a/schema-next.yaml +++ b/schema-next.yaml @@ -2,6 +2,7 @@ file_format: 1.1.0 schema_url: https://opentelemetry.io/schemas/next versions: next: + 1.30.0: all: changes: # https://github.com/open-telemetry/semantic-conventions/pull/1632 @@ -16,7 +17,9 @@ versions: code.filepath: code.file.path code.lineno: code.line.number code.column: code.column.number - # https://github.com/open-telemetry/semantic-conventions/pull/TODO + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1734 - rename_attributes: attribute_map: db.system: db.system.name diff --git a/schemas/1.30.0 b/schemas/1.30.0 new file mode 100644 index 0000000000..a157c08b6a --- /dev/null +++ b/schemas/1.30.0 @@ -0,0 +1,580 @@ +file_format: 1.1.0 +schema_url: https://opentelemetry.io/schemas/1.30.0 +versions: + 1.30.0: + all: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1632 + - rename_attributes: + attribute_map: + gen_ai.openai.request.seed: gen_ai.request.seed + system.network.state: network.connection.state + # https://github.com/open-telemetry/semantic-conventions/pull/1624 + - rename_attributes: + attribute_map: + code.function: code.function.name + code.filepath: code.file.path + code.lineno: code.line.number + code.column: code.column.number + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1734 + - rename_attributes: + attribute_map: + db.system: db.system.name + db.cassandra.coordinator.dc: cassandra.coordinator.dc + db.cassandra.coordinator.id: cassandra.coordinator.id + db.cassandra.consistency_level: cassandra.consistency.level + db.cassandra.idempotence: cassandra.query.idempotent + db.cassandra.page_size: cassandra.page.size + db.cassandra.speculative_execution_count: cassandra.speculative_execution.count + db.cosmosdb.client_id: azure.client.id + db.cosmosdb.connection_mode: azure.cosmosdb.connection.mode + db.cosmosdb.consistency_level: azure.cosmosdb.consistency.level + db.cosmosdb.request_charge: azure.cosmosdb.operation.request_charge + db.cosmosdb.request_content_length: azure.cosmosdb.request.body.size + db.cosmosdb.regions_contacted: azure.cosmosdb.operation.contacted_regions + db.cosmosdb.sub_status_code: azure.cosmosdb.response.sub_status_code + db.elasticsearch.node.name: elasticsearch.node.name + # db.elasticsearch.path_parts is a template attribute, schema transformation + # does not support it, adding as a comment for consistency + # db.elasticsearch.path_parts. -> db.operation.parameter. + - rename_metrics: + db.client.cosmosdb.operation.request_charge: azure.cosmosdb.client.operation.request_charge + db.client.cosmosdb.active_instance.count: azure.cosmosdb.client.active_instance.count + + 1.29.0: + all: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1520 + - rename_attributes: + attribute_map: + process.executable.build_id.profiling: process.executable.build_id.htlhash + # https://github.com/open-telemetry/semantic-conventions/pull/1383 + - rename_attributes: + attribute_map: + vcs.repository.change.id: vcs.change.id + vcs.repository.change.title: vcs.change.title + vcs.repository.ref.name: vcs.ref.head.name + vcs.repository.ref.revision: vcs.ref.head.revision + vcs.repository.ref.type: vcs.ref.head.type + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1492 + - rename_attributes: + attribute_map: + system.device: network.interface.name + apply_to_metrics: + - container.network.io + - system.network.dropped + - system.network.errors + - system.network.io + - system.network.connections + 1.28.0: + metrics: + changes: + # https://github.com/open-telemetry/semantic-conventions/pull/1422 + - rename_metrics: + messaging.client.published.messages: messaging.client.sent.messages + 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.eventhubs.consumer.group: messaging.consumer.group.name + messaging.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: