From eff768d1384d3ad253216a970014a7ffca1eef2d Mon Sep 17 00:00:00 2001 From: bachgarash Date: Fri, 14 Nov 2025 21:57:37 +0400 Subject: [PATCH 1/5] feat: introduce new service.criticality attribute (#2986) --- .chloggen/service-criticality-attribute.yaml | 25 ++++++++++++ docs/registry/attributes/service.md | 34 +++++++++++++--- docs/registry/entities/service.md | 3 ++ docs/resource/README.md | 3 ++ model/service/entities.yaml | 2 + model/service/registry.yaml | 42 ++++++++++++++++++++ 6 files changed, 103 insertions(+), 6 deletions(-) create mode 100644 .chloggen/service-criticality-attribute.yaml diff --git a/.chloggen/service-criticality-attribute.yaml b/.chloggen/service-criticality-attribute.yaml new file mode 100644 index 0000000000..8389b37951 --- /dev/null +++ b/.chloggen/service-criticality-attribute.yaml @@ -0,0 +1,25 @@ +# 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: "service" + +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). +note: "Add `service.criticality` attribute to classify services based on operational importance" + +# 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: [2986] + +# (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 attribute enables observability platforms to implement criticality-aware tracing, monitoring, + and sampling strategies. Supports four levels: critical, high, medium, and low. + diff --git a/docs/registry/attributes/service.md b/docs/registry/attributes/service.md index a5d3f6be08..be4ef2fcb8 100644 --- a/docs/registry/attributes/service.md +++ b/docs/registry/attributes/service.md @@ -11,12 +11,15 @@ A service instance. | Key | Stability | Value Type | Description | Example Values | |---|---|---|---|---| -| `service.instance.id` | ![Development](https://img.shields.io/badge/-development-blue) | string | The string ID of the service instance. [1] | `627cc493-f310-47de-96bd-71410b7dec09` | -| `service.name` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | string | Logical name of the service. [2] | `shoppingcart` | -| `service.namespace` | ![Development](https://img.shields.io/badge/-development-blue) | string | A namespace for `service.name`. [3] | `Shop` | +| `service.criticality` | ![Development](https://img.shields.io/badge/-development-blue) | string | The operational criticality of the service. [1] | `critical`; `high`; `medium`; `low` | +| `service.instance.id` | ![Development](https://img.shields.io/badge/-development-blue) | string | The string ID of the service instance. [2] | `627cc493-f310-47de-96bd-71410b7dec09` | +| `service.name` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | string | Logical name of the service. [3] | `shoppingcart` | +| `service.namespace` | ![Development](https://img.shields.io/badge/-development-blue) | string | A namespace for `service.name`. [4] | `Shop` | | `service.version` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | string | The version string of the service API or implementation. The format is not defined by these conventions. | `2.0.0`; `a01dbef8a` | -**[1] `service.instance.id`:** MUST be unique for each instance of the same `service.namespace,service.name` pair (in other words +**[1] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. + +**[2] `service.instance.id`:** MUST be unique for each instance of the same `service.namespace,service.name` pair (in other words `service.namespace,service.name,service.instance.id` triplet MUST be globally unique). The ID helps to distinguish instances of the same service that exist at the same time (e.g. instances of a horizontally scaled service). @@ -43,6 +46,25 @@ However, Collectors can set the `service.instance.id` if they can unambiguously for that telemetry. This is typically the case for scraping receivers, as they know the target address and port. -**[2] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`. +**[3] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`. + +**[4] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. + +--- + +`service.criticality` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used. + +| Value | Description | Stability | +|---|---|---| +| `critical` | Service is business-critical; downtime directly impacts revenue, user experience, or core functionality. [5] | ![Development](https://img.shields.io/badge/-development-blue) | +| `high` | Service is important but has degradation tolerance or fallback mechanisms. [6] | ![Development](https://img.shields.io/badge/-development-blue) | +| `low` | Service is non-essential to core operations; used for background tasks or internal tools. [7] | ![Development](https://img.shields.io/badge/-development-blue) | +| `medium` | Service provides supplementary functionality; degradation has limited user impact. [8] | ![Development](https://img.shields.io/badge/-development-blue) | + +**[5]:** Examples include payment processing, authentication, and primary user-facing APIs. + +**[6]:** Examples include shopping cart, search, and recommendation engines. + +**[7]:** Examples include batch processors, cleanup jobs, and internal dashboards. -**[3] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. +**[8]:** Examples include analytics, reporting, and non-essential integrations. diff --git a/docs/registry/entities/service.md b/docs/registry/entities/service.md index fefd081b16..f66358bdf6 100644 --- a/docs/registry/entities/service.md +++ b/docs/registry/entities/service.md @@ -18,6 +18,7 @@ | Identity | [`service.name`](/docs/registry/attributes/service.md) | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | `Required` | string | Logical name of the service. [1] | `shoppingcart` | | Identity | [`service.instance.id`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | The string ID of the service instance. [2] | `627cc493-f310-47de-96bd-71410b7dec09` | | Identity | [`service.namespace`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | A namespace for `service.name`. [3] | `Shop` | +| Description | [`service.criticality`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | The operational criticality of the service. [4] | `critical`; `high`; `medium`; `low` | | Description | [`service.version`](/docs/registry/attributes/service.md) | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | `Recommended` | string | The version string of the service API or implementation. The format is not defined by these conventions. | `2.0.0`; `a01dbef8a` | **[1] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`. @@ -51,4 +52,6 @@ port. **[3] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. +**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. + diff --git a/docs/resource/README.md b/docs/resource/README.md index e623253d5b..6c61bdc485 100644 --- a/docs/resource/README.md +++ b/docs/resource/README.md @@ -84,6 +84,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet | Identity | [`service.name`](/docs/registry/attributes/service.md) | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | `Required` | string | Logical name of the service. [1] | `shoppingcart` | | Identity | [`service.instance.id`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | The string ID of the service instance. [2] | `627cc493-f310-47de-96bd-71410b7dec09` | | Identity | [`service.namespace`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | A namespace for `service.name`. [3] | `Shop` | +| Description | [`service.criticality`](/docs/registry/attributes/service.md) | ![Development](https://img.shields.io/badge/-development-blue) | `Recommended` | string | The operational criticality of the service. [4] | `critical`; `high`; `medium`; `low` | | Description | [`service.version`](/docs/registry/attributes/service.md) | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | `Recommended` | string | The version string of the service API or implementation. The format is not defined by these conventions. | `2.0.0`; `a01dbef8a` | **[1] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`. @@ -116,6 +117,8 @@ for that telemetry. This is typically the case for scraping receivers, as they k port. **[3] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. + +**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. diff --git a/model/service/entities.yaml b/model/service/entities.yaml index 319eb39eae..8fa7f4d7b9 100644 --- a/model/service/entities.yaml +++ b/model/service/entities.yaml @@ -15,3 +15,5 @@ groups: role: identifying - ref: service.instance.id role: identifying + - ref: service.criticality + role: descriptive diff --git a/model/service/registry.yaml b/model/service/registry.yaml index 9715378b19..18cf9aa3d1 100644 --- a/model/service/registry.yaml +++ b/model/service/registry.yaml @@ -69,3 +69,45 @@ groups: for that telemetry. This is typically the case for scraping receivers, as they know the target address and port. examples: ["627cc493-f310-47de-96bd-71410b7dec09"] + - id: service.criticality + type: + members: + - id: critical + value: 'critical' + brief: > + Service is business-critical; downtime directly impacts revenue, user experience, or core functionality. + note: > + Examples include payment processing, authentication, and primary user-facing APIs. + stability: development + - id: high + value: 'high' + brief: > + Service is important but has degradation tolerance or fallback mechanisms. + note: > + Examples include shopping cart, search, and recommendation engines. + stability: development + - id: medium + value: 'medium' + brief: > + Service provides supplementary functionality; degradation has limited user impact. + note: > + Examples include analytics, reporting, and non-essential integrations. + stability: development + - id: low + value: 'low' + brief: > + Service is non-essential to core operations; used for background tasks or internal tools. + note: > + Examples include batch processors, cleanup jobs, and internal dashboards. + stability: development + stability: development + brief: > + The operational criticality of the service. + note: > + This attribute enables classification of services based on their operational importance, + allowing observability platforms to implement criticality-aware tracing, monitoring, + and sampling strategies. By standardizing service criticality, organizations can implement + adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize + telemetry costs by reducing data from non-critical services, improve incident response by + surfacing critical service traces first, and enable better capacity planning and resource allocation. + examples: ["critical", "high", "medium", "low"] From 3a066a1ddef5554473b5d8dd928571e0f38b8373 Mon Sep 17 00:00:00 2001 From: bachgarash Date: Tue, 18 Nov 2025 00:28:30 +0400 Subject: [PATCH 2/5] feat: make yamllint happy --- .chloggen/service-criticality-attribute.yaml | 1 - areas.yaml | 4 ++-- internal/tools/scripts/schema-diff/yaml/weaver.yaml | 2 +- model/service/registry.yaml | 10 +++++----- 4 files changed, 8 insertions(+), 9 deletions(-) diff --git a/.chloggen/service-criticality-attribute.yaml b/.chloggen/service-criticality-attribute.yaml index 8389b37951..ab8455bc57 100644 --- a/.chloggen/service-criticality-attribute.yaml +++ b/.chloggen/service-criticality-attribute.yaml @@ -22,4 +22,3 @@ issues: [2986] subtext: | This attribute enables observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. Supports four levels: critical, high, medium, and low. - diff --git a/areas.yaml b/areas.yaml index 058c08b2c5..546f05d338 100644 --- a/areas.yaml +++ b/areas.yaml @@ -105,7 +105,7 @@ areas: - name: "Semantic Conventions: Resources and Entities" owner: - - name: "specs-semconv-maintainers" # TODO: Missing team user for entities? + - name: "specs-semconv-maintainers" # TODO: Missing team user for entities? github: specs-semconv-maintainers project: "https://github.com/open-telemetry/community/blob/main/projects/resources-and-entities.md" board: "https://github.com/orgs/open-telemetry/projects/85" @@ -158,7 +158,7 @@ areas: - name: "Semantic Conventions: FaaS" owner: - - name: "specs-semconv-maintainers" # TODO: Missing team user for faas? + - name: "specs-semconv-maintainers" # TODO: Missing team user for faas? github: specs-semconv-maintainers project: "https://github.com/open-telemetry/community/blob/main/projects/completed-projects/faas.md" board: "N/A" diff --git a/internal/tools/scripts/schema-diff/yaml/weaver.yaml b/internal/tools/scripts/schema-diff/yaml/weaver.yaml index 702545a9e1..4b45921cff 100644 --- a/internal/tools/scripts/schema-diff/yaml/weaver.yaml +++ b/internal/tools/scripts/schema-diff/yaml/weaver.yaml @@ -1,5 +1,5 @@ params: - next_version: "next_version_placeholder" # https://github.com/open-telemetry/weaver/issues/775 + next_version: "next_version_placeholder" # https://github.com/open-telemetry/weaver/issues/775 templates: - pattern: schema-diff.j2 filter: > diff --git a/model/service/registry.yaml b/model/service/registry.yaml index 18cf9aa3d1..9c649f8d16 100644 --- a/model/service/registry.yaml +++ b/model/service/registry.yaml @@ -104,10 +104,10 @@ groups: brief: > The operational criticality of the service. note: > - This attribute enables classification of services based on their operational importance, - allowing observability platforms to implement criticality-aware tracing, monitoring, - and sampling strategies. By standardizing service criticality, organizations can implement - adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize - telemetry costs by reducing data from non-critical services, improve incident response by + This attribute enables classification of services based on their operational importance, + allowing observability platforms to implement criticality-aware tracing, monitoring, + and sampling strategies. By standardizing service criticality, organizations can implement + adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize + telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. examples: ["critical", "high", "medium", "low"] From a93a6f0121fb096e918209ba9b5371acc6e0793c Mon Sep 17 00:00:00 2001 From: bachgarash Date: Tue, 18 Nov 2025 11:25:30 +0400 Subject: [PATCH 3/5] feat: update attribute registry markdown --- docs/registry/attributes/service.md | 2 +- docs/registry/entities/service.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/registry/attributes/service.md b/docs/registry/attributes/service.md index be4ef2fcb8..ec8c62389c 100644 --- a/docs/registry/attributes/service.md +++ b/docs/registry/attributes/service.md @@ -17,7 +17,7 @@ A service instance. | `service.namespace` | ![Development](https://img.shields.io/badge/-development-blue) | string | A namespace for `service.name`. [4] | `Shop` | | `service.version` | ![Stable](https://img.shields.io/badge/-stable-lightgreen) | string | The version string of the service API or implementation. The format is not defined by these conventions. | `2.0.0`; `a01dbef8a` | -**[1] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. +**[1] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. **[2] `service.instance.id`:** MUST be unique for each instance of the same `service.namespace,service.name` pair (in other words `service.namespace,service.name,service.instance.id` triplet MUST be globally unique). The ID helps to diff --git a/docs/registry/entities/service.md b/docs/registry/entities/service.md index f66358bdf6..47f57cdf3b 100644 --- a/docs/registry/entities/service.md +++ b/docs/registry/entities/service.md @@ -52,6 +52,6 @@ port. **[3] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. -**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. +**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. From 7e9b3a1c3c678dc4d9b4b1c34e225ebe21ea6aea Mon Sep 17 00:00:00 2001 From: bachgarash Date: Thu, 20 Nov 2025 20:09:39 +0400 Subject: [PATCH 4/5] feat: add requirement level and rerun table generation --- docs/resource/README.md | 2 +- model/service/entities.yaml | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/resource/README.md b/docs/resource/README.md index 6c61bdc485..de4a88b7cc 100644 --- a/docs/resource/README.md +++ b/docs/resource/README.md @@ -118,7 +118,7 @@ port. **[3] `service.namespace`:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace. -**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. +**[4] `service.criticality`:** This attribute enables classification of services based on their operational importance, allowing observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. By standardizing service criticality, organizations can implement adaptive sampling rates (e.g., 100% for critical, 10% for low-priority services), optimize telemetry costs by reducing data from non-critical services, improve incident response by surfacing critical service traces first, and enable better capacity planning and resource allocation. diff --git a/model/service/entities.yaml b/model/service/entities.yaml index 8fa7f4d7b9..4b2194d07b 100644 --- a/model/service/entities.yaml +++ b/model/service/entities.yaml @@ -16,4 +16,6 @@ groups: - ref: service.instance.id role: identifying - ref: service.criticality + requirement_level: recommended role: descriptive + From bf07d66a99ce8f206ae3ba94a0494216a53e3171 Mon Sep 17 00:00:00 2001 From: bachgarash Date: Thu, 20 Nov 2025 20:36:52 +0400 Subject: [PATCH 5/5] feat: fix yamllint --- model/service/entities.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/model/service/entities.yaml b/model/service/entities.yaml index 4b2194d07b..31ff65d094 100644 --- a/model/service/entities.yaml +++ b/model/service/entities.yaml @@ -18,4 +18,3 @@ groups: - ref: service.criticality requirement_level: recommended role: descriptive -