semconv.com — What changed in OpenTelemetry since you last looked https://semconv.com A version-by-version record of the OpenTelemetry semantic conventions, specification and OTLP: which attributes were renamed, which requirements appeared in a stable document, and which fields changed on the wire. en Specification v1.60.0 — 6 breaking, 8 notable https://semconv.com/releases/spec/1.60.0 https://semconv.com/releases/spec/1.60.0 Fri, 07 Aug 2026 15:52:31 GMT 6 breaking, 8 notable, 17 editorial changes since v1.59.0. BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST added: Enabled: If the `Logger` is not enabled (i.e. `LoggerConfig.enabled` is `false`), the log record MUST be dropped. BREAKING · requirement requirement-added · specification/resource/sdk.md#create — MUST added: When both `Entities` and `Attributes` are provided in the create method, the system MUST behave as if a Resource is created with just `Attributes` and then merges with another Resource created with just `Entities`. BREAKING · requirement requirement-added · specification/resource/sdk.md#merge — MUST added: If either resource contains `Entities` then merge behavior with Entiites MUST be used, otherwise merge behavior without Entities MUST be used. BREAKING · requirement requirement-added · specification/resource/sdk.md#merge-behavior-with-entities — MUST added: When either Resource contains entities, the merge operation MUST follow the resource data model's merge algorithm. BREAKING · requirement requirement-added · specification/resource/sdk.md#merge-behavior-with-entities — MUST added: The resulting `SchemaURL` MUST match the behavior defined in the merge algorithm. BREAKING · requirement requirement-added · specification/resource/sdk.md#retrieve-attributes — MUST added: When entities are enabled and present for the Resource, this list MUST include all attributes, including those associated with entities. NOTABLE · requirement requirement-removed · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST removed: The content negotiation requirements MUST take precedence over the configured translation strategy when determining the final output format. NOTABLE · requirement requirement-removed · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST removed: If configured with `NoTranslation` but the client requests `escaping=underscores`, the exporter MUST apply underscore escaping. NOTABLE · requirement requirement-added · specification/logs/api.md#enabled — SHOULD added: The API documentation SHOULD state that calling `Enabled` is optional and is not required before emitting a `LogRecord`. NOTABLE · requirement requirement-added · specification/logs/api.md#enabled — SHOULD added: The documentation SHOULD also state that the returned value is not static and can change over time, so a cached value can become stale. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST added: First, `translation_strategy` MUST be applied to construct metric names. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST added: Then, the Prometheus Exporter MUST apply content negotiation, which may include a second translation of metric names using the requested escaping scheme. NOTABLE · requirement requirement-added · specification/resource/sdk.md#retrieve-entities — SHOULD added: The SDK SHOULD provide a way to retrieve the entities associated with a resource. NOTABLE · requirement requirement-added · specification/resource/sdk.md#retrieve-unassociated-attributes — SHOULD added: The SDK SHOULD provide a way to retrieve attributes which are NOT associated with an entity in the resource. Semantic conventions v1.44.0 — 3 breaking, 21 notable https://semconv.com/releases/semconv/1.44.0 https://semconv.com/releases/semconv/1.44.0 Tue, 04 Aug 2026 20:00:58 GMT 3 breaking, 21 notable, 92 editorial changes since v1.43.0. BREAKING · metric instrument-changed · container.memory.usage — Instrument changed from `counter` to `updowncounter`. BREAKING · metric instrument-changed · k8s.node.memory.usage — Instrument changed from `gauge` to `updowncounter`. BREAKING · metric instrument-changed · k8s.pod.memory.usage — Instrument changed from `gauge` to `updowncounter`. NOTABLE · signal removed · span.faas.client — Removed from the registry (was development). NOTABLE · signal removed · span.faas.datasource.server — Removed from the registry (was development). NOTABLE · signal removed · span.faas.server — Removed from the registry (was development). NOTABLE · signal removed · span.faas.timer.server — Removed from the registry (was development). NOTABLE · metric renamed · container.memory.paging.faults — Renamed to `container.paging.faults`. NOTABLE · metric renamed · k8s.node.memory.paging.faults — Renamed to `k8s.node.paging.faults`. NOTABLE · metric renamed · k8s.pod.memory.paging.faults — Renamed to `k8s.pod.paging.faults`. NOTABLE · attribute deprecated · db.redis.database_index — Replaced by `db.namespace` (string). NOTABLE · metric stability-changed · container.memory.available — Promoted to release_candidate. NOTABLE · metric stability-changed · container.memory.rss — Promoted to release_candidate. NOTABLE · metric stability-changed · container.memory.usage — Promoted to release_candidate. NOTABLE · metric stability-changed · container.memory.working_set — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.node.memory.available — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.node.memory.rss — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.node.memory.usage — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.node.memory.working_set — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.pod.memory.available — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.pod.memory.rss — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.pod.memory.usage — Promoted to release_candidate. NOTABLE · metric stability-changed · k8s.pod.memory.working_set — Promoted to release_candidate. NOTABLE · attribute stability-changed · network.interface.name — Promoted to release_candidate. OTLP v1.11.0 — 0 breaking, 14 notable https://semconv.com/releases/proto/1.11.0 https://semconv.com/releases/proto/1.11.0 Tue, 21 Jul 2026 13:54:02 GMT 0 breaking, 14 notable, 29 editorial changes since v1.10.0. NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-request — MUST added: The server MUST enforce a message size limit when receiving the request, including after decompression, to mitigate possible excessive memory usage caused by a misconfigured or malicious client sending an oversized requ... NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-request — MUST added: If the limit is exceeded, the gRPC server implementations MUST report a `RESOURCE_EXHAUSTED` code as a non-retryable error. NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-request — MUST NOT added: If the limit is exceeded, the client MUST NOT make the request and SHOULD record the fact that the request was discarded. NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-response — MUST added: The client MUST enforce a message size limit when receiving the response, including after decompression, to mitigate possible excessive memory usage caused by a misconfigured or malicious server. gRPC client implementat... NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-response — MUST added: If the limit is exceeded, the client MUST treat the response as a non-retryable error. NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-response — MUST added: The server MUST limit the size of the response message, including before compression, to avoid overwhelming the client. NOTABLE · requirement requirement-added · docs/specification.md#otlpgrpc-response — MUST added: If the response still cannot fit within the limit, the server MUST fail the request with the `RESOURCE_EXHAUSTED` code as a non-retryable error. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-request — MUST added: The server MUST limit the size of the request body when parsing it, including after decompression, to mitigate possible excessive memory usage caused by a misconfigured or malicious client sending an oversized request. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-request — MUST added: If the limit is exceeded, the server MUST respond with `HTTP 413 Content Too Large`. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-request — MUST NOT added: If the limit is exceeded, the client MUST NOT make the request and SHOULD record the fact that the request was discarded. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-response — MUST added: The client MUST limit the size of the response body when parsing it, including after decompression, to mitigate possible excessive memory usage caused by a misconfigured or malicious server. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-response — MUST added: If the limit is exceeded, the client MUST treat the response as a non-retryable error and SHOULD record the fact that the response was discarded. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-response — MUST added: The server MUST limit the size of the response body, including before compression, to avoid overwhelming the client. NOTABLE · requirement requirement-added · docs/specification.md#otlphttp-response — MUST added: If the response still cannot fit within the limit, the server MUST fail the request with `HTTP 500 Internal Server Error`. Specification v1.59.0 — 2 breaking, 4 notable https://semconv.com/releases/spec/1.59.0 https://semconv.com/releases/spec/1.59.0 Fri, 10 Jul 2026 14:21:51 GMT 2 breaking, 4 notable, 41 editorial changes since v1.58.0. BREAKING · requirement requirement-removed · specification/context/env-carriers.md#process-spawning — MUST NOT removed: The language implementations MUST NOT handle spawning processes. BREAKING · requirement requirement-added · specification/context/env-carriers.md#propagator-mechanisms — MUST NOT added: Language implementations MUST NOT spawn child processes as part of environment variable context propagation. NOTABLE · document stability-changed · specification/context/env-carriers.md — Status changed from Beta to Release Candidate. NOTABLE · document stability-changed · specification/profiles/data-format.md — Status changed from Development to Alpha. NOTABLE · requirement requirement-added · specification/context/env-carriers.md#propagator-mechanisms — SHOULD added: Language implementations SHOULD document operational guidance, including initialization-time extraction, child process environment handling, and security considerations. NOTABLE · requirement requirement-added · specification/trace/sdk.md#getsamplingintent — SHOULD added: The calling CompositeSampler SHOULD update the threshold of the outgoing TraceState, as described above. Semantic conventions v1.43.0 — 1 breaking, 73 notable https://semconv.com/releases/semconv/1.43.0 https://semconv.com/releases/semconv/1.43.0 Fri, 03 Jul 2026 20:14:31 GMT 1 breaking, 73 notable, 22 editorial changes since v1.42.0. BREAKING · metric unit-changed · cicd.worker.count — Unit changed from `{count}` to `{worker}`. NOTABLE · signal removed · entity.vcs.repo — Removed from the registry (was development). NOTABLE · attribute stability-changed · cicd.pipeline.action.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.result — Promoted to release_candidate. NOTABLE · metric stability-changed · cicd.pipeline.run.active — Promoted to release_candidate. NOTABLE · metric stability-changed · cicd.pipeline.run.duration — Promoted to release_candidate. NOTABLE · metric stability-changed · cicd.pipeline.run.errors — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.run.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.run.state — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.run.url.full — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.task.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.task.run.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.task.run.result — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.task.run.url.full — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.pipeline.task.type — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.system.component — Promoted to release_candidate. NOTABLE · metric stability-changed · cicd.system.errors — Promoted to release_candidate. NOTABLE · metric stability-changed · cicd.worker.count — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.worker.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.worker.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.worker.state — Promoted to release_candidate. NOTABLE · attribute stability-changed · cicd.worker.url.full — Promoted to release_candidate. NOTABLE · attribute stability-changed · disk.io.direction — Promoted to release_candidate. NOTABLE · signal stability-changed · entity.cicd.pipeline — Promoted to release_candidate. NOTABLE · signal stability-changed · entity.cicd.pipeline.run — Promoted to release_candidate. NOTABLE · signal stability-changed · entity.cicd.worker — Promoted to release_candidate. NOTABLE · signal stability-changed · entity.process — Promoted to release_candidate. NOTABLE · attribute stability-changed · network.io.direction — Promoted to release_candidate. NOTABLE · attribute stability-changed · oracle.db.domain — Promoted to release_candidate. …and 44 more. Specification v1.58.0 — 0 breaking, 44 notable https://semconv.com/releases/spec/1.58.0 https://semconv.com/releases/spec/1.58.0 Mon, 22 Jun 2026 16:02:03 GMT 0 breaking, 44 notable, 60 editorial changes since v1.57.0. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#histograms-1 — MUST removed: The final bucket metric MUST have an `+Inf` threshold. NOTABLE · document stability-changed · specification/compatibility/opencensus.md — Status changed from Stable to Deprecated. NOTABLE · document stability-changed · specification/profiles/mappings.md — Status changed from Development to Alpha. NOTABLE · document stability-changed · specification/profiles/pprof.md — Status changed from Development to Alpha. NOTABLE · document stability-changed · specification/profiles/README.md — Status changed from Unspecified to Alpha. NOTABLE · requirement requirement-added · specification/common/README.md#arrays — SHOULD added: Array elements SHOULD be represented as JSON values using the following rules: NOTABLE · requirement requirement-added · specification/common/README.md#attribute-collection-representation-for-non-otlp — RECOMMENDED added: For non-OTLP protocols that need to represent an Attribute Collection as a string, the RECOMMENDED form is a JSON object. NOTABLE · requirement requirement-added · specification/common/README.md#attribute-collection-representation-for-non-otlp — SHOULD added: Each attribute key SHOULD be represented as a JSON object member name. NOTABLE · requirement requirement-added · specification/common/README.md#attribute-collection-representation-for-non-otlp — SHOULD added: Each attribute value SHOULD be represented as the corresponding JSON object member value and follow the encoding rules defined in AnyValue representation for non-OTLP protocols, as it would be represented as an element ... NOTABLE · requirement requirement-added · specification/common/README.md#attribute-representation-for-non-otlp — RECOMMENDED added: For non-OTLP protocols that need to represent a single `Attribute` as a string, the RECOMMENDED form is a JSON object containing a single name/value pair (member). NOTABLE · requirement requirement-added · specification/common/README.md#attribute-representation-for-non-otlp — SHOULD added: The attribute key SHOULD be represented as a JSON object member name. NOTABLE · requirement requirement-added · specification/common/README.md#attribute-representation-for-non-otlp — SHOULD added: The attribute value SHOULD be represented as a JSON object member value and follow the encoding rules defined in AnyValue representation for non-OTLP protocols, as it would be represented as an element in an array and a... NOTABLE · requirement requirement-added · specification/common/README.md#maps — SHOULD added: Map keys SHOULD be represented as JSON string member names. NOTABLE · requirement requirement-added · specification/common/README.md#maps — SHOULD added: Map values SHOULD be represented using the same rules as array elements. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-histograms — MUST added: When converting to a Prometheus Histogram, an OpenTelemetry Histogram MUST be converted following the rules below: NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: When converting to a Prometheus NHCB, only a single NHCB metric MUST be created: NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: The flavor of the NHCB MUST be integer counter. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: The `ResetHint` in the NHCB MUST be set to `UNKNOWN`. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: The `Schema` in the NHCB MUST be set to -53. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST NOT added: The implicit `+Inf` upper bound MUST NOT be written into `CustomValues`; it is represented by the overflow bucket at index `len(CustomValues)`. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: All fields of the NHCB that are not explicitly referenced here MUST be set to their zero value, such as zero threshold, zero count, negative spans, negative deltas, etc. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: If the `NoRecordedValue` flag is set to `true`, the NHCB MUST be marked as stale: NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: The Native Histogram `Sum` MUST be set to the Stale NaN value. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: The Native Histogram `Count` MUST be set to zero. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: `PositiveSpans` and `PositiveDeltas` MUST be left empty. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#histograms-as-prometheus-nhcb — MUST added: Non-zero bucket counts MUST be converted into `PositiveDeltas`. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#summaries-1 — MUST added: The `quantile` label value MUST be the stringified floating point value of each quantile (between 0.0 and 1.0), starting from lowest to highest, and all being non-negative. NOTABLE · requirement requirement-added · specification/context/env-carriers.md#key-name-normalization — MUST added: To normalize a key name, implementations MUST: NOTABLE · requirement requirement-added · specification/context/env-carriers.md#key-name-normalization — MUST added: `Set` MUST write values using the normalized form of the key provided by the propagator. NOTABLE · requirement requirement-added · specification/context/env-carriers.md#key-name-normalization — MUST added: `Get` MUST normalize the key requested by the propagator and MUST use the normalized key name to read from the carrier. …and 14 more. Semantic conventions v1.42.0 — 0 breaking, 179 notable https://semconv.com/releases/semconv/1.42.0 https://semconv.com/releases/semconv/1.42.0 Fri, 12 Jun 2026 21:03:17 GMT 0 breaking, 179 notable, 151 editorial changes since v1.41.1. NOTABLE · metric renamed · v8js.memory.heap.limit — Renamed to `v8js.memory.heap.space.size`. NOTABLE · signal deprecated · event.gen_ai.client.inference.operation.details — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · signal deprecated · event.gen_ai.client.operation.exception — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · signal deprecated · event.gen_ai.evaluation.result — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.agent.description — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.agent.id — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.agent.name — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.agent.version — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · metric deprecated · gen_ai.client.operation.duration — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · metric deprecated · gen_ai.client.operation.time_per_output_chunk — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · metric deprecated · gen_ai.client.operation.time_to_first_chunk — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · metric deprecated · gen_ai.client.token.usage — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.conversation.id — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.data_source.id — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.embeddings.dimension.count — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.evaluation.explanation — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.evaluation.name — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.evaluation.score.label — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.evaluation.score.value — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.input.messages — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.openai.request.response_format — Replaced by `gen_ai.output.type`, which has moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conve... NOTABLE · attribute deprecated · gen_ai.openai.request.seed — Replaced by `gen_ai.request.seed`, which has moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conv... NOTABLE · attribute deprecated · gen_ai.openai.request.service_tier — Replaced by `openai.request.service_tier`, which has moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/seman... NOTABLE · attribute deprecated · gen_ai.openai.response.service_tier — Replaced by `openai.response.service_tier`, which has moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/sema... NOTABLE · attribute deprecated · gen_ai.openai.response.system_fingerprint — Replaced by `openai.response.system_fingerprint`, which has moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetr... NOTABLE · attribute deprecated · gen_ai.operation.name — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.output.messages — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.output.type — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.prompt.name — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). NOTABLE · attribute deprecated · gen_ai.provider.name — Moved to the [OpenTelemetry GenAI semantic conventions repository](https://github.com/open-telemetry/semantic-conventions-genai). …and 149 more. Specification v1.57.0 — 5 breaking, 22 notable https://semconv.com/releases/spec/1.57.0 https://semconv.com/releases/spec/1.57.0 Wed, 20 May 2026 15:27:35 GMT 5 breaking, 22 notable, 22 editorial changes since v1.56.0. BREAKING · requirement requirement-added · specification/metrics/api.md#bind — MUST added: This API MUST accept the following parameter: BREAKING · requirement requirement-added · specification/metrics/api.md#bind — MUST added: Therefore, this API MUST be structured to accept a variable number of attributes, including none. BREAKING · requirement requirement-added · specification/metrics/api.md#bind — MUST added: This API MUST return a language-idiomatic type representing the instrument bound to those attributes. BREAKING · requirement requirement-added · specification/metrics/api.md#bind — MUST added: The returned bound instrument MUST support the instrument's core recording operation. BREAKING · requirement requirement-added · specification/metrics/api.md#bind — MUST added: If the existing instrument interface is reused, the `Bind` API MUST be documented to communicate to users that invoking attribute-bearing recording operations on the returned bound instrument negates the performance ben... NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#gauges-1 — MUST removed: Otherwise, it MUST be converted to a Prometheus Gauge. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope-1 — MUST removed: Scope attributes with names 'name', 'version', or 'schemaurl' MUST be dropped to avoid conflicts with the already existing `otelscopename`, `otelscopeversion`, and `otelscopeschema_url` labels. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#sums — MUST removed: If the aggregation temporality is cumulative and the sum is non-monotonic and the `prometheus.type` key of [metric.metadata][metricMetadata] is `stateset`, it MUST be converted to an OpenMetrics StateSet metric. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#sums — MUST removed: If the aggregation temporality is cumulative and the sum is non-monotonic, it MUST be converted to a Prometheus Gauge. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#sums — MUST removed: Otherwise, it MUST be dropped. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#sums — MUST relaxed to MAY: If the aggregation temporality is delta and the sum is monotonic, it MAY be converted to a cumulative temporality and become a Prometheus Counter. NOTABLE · requirement requirement-level-changed · specification/metrics/sdk_exporters/prometheus.md#client-libraries — SHOULD relaxed to SHOULD NOT: A Prometheus Exporter SHOULD use an official Prometheus client library when one exists for the implementation language and it is practical to do so (e.g., dependency concerns) for serving Prometheus ... NOTABLE · requirement requirement-level-changed · specification/metrics/sdk_exporters/prometheus.md#version-and-format — MUST NOT relaxed to SHOULD NOT: A Prometheus Exporter for an OpenTelemetry metrics SDK SHOULD NOT add explicit timestamps on Metric points. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#gauges-1 — MUST added: If the `prometheus.type` key is absent, or its value is equal to `gauge`, the datapoint MUST be transformed to a Prometheus Gauge. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#gauges-1 — MUST added: If the `prometheus.type` key has value equal to `unkown`, the datapoint MUST be transformed to a Prometheus Unknown. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope-1 — MUST added: Scope attributes that, after adding the `otelscope` prefix and applying the label-name conversion described in `Metric Attributes`, would conflict with `otelscopename`, `otelscopeversion`, or `otelscopeschemaurl` MUST b... NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#sums — MUST added: An OpenTelemetry Sum MUST be converted following the rules below: NOTABLE · requirement requirement-added · specification/metrics/api.md#bind — MAY added: This MAY be achieved by introducing a dedicated bound instrument type, or by reusing the existing instrument interface. NOTABLE · requirement requirement-added · specification/metrics/api.md#general-operations — MAY added: All synchronous instruments MAY provide: NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: A bound instrument MUST behave identically to calling the equivalent unbound recording operation with the pre-bound Attributes on each measurement. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: Attribute processing and cardinality limit evaluation MUST be performed at bind time. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: Each call to `Bind` MUST be independently evaluated against the cardinality state at that moment. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: The resolved aggregator MUST be fixed and not change across collection cycles. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: Measurements recorded on a bound instrument MUST be candidates for Exemplar sampling. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: The Context associated with each recording, whether implicit or explicit, MUST be used for exemplar TraceBased filtering and passed to the ExemplarReservoir offer method. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-bind — MUST added: The SDK MUST ensure attribute-free recordings on a bound instrument bypass per-recording map lookup. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#stream-configuration — MUST NOT added: The `name` provided via stream configuration is NOT REQUIRED to conform to the instrument name syntax, and the SDK MUST NOT validate it against that syntax. Semantic conventions v1.41.1 — 0 breaking, 0 notable https://semconv.com/releases/semconv/1.41.1 https://semconv.com/releases/semconv/1.41.1 Mon, 11 May 2026 22:28:25 GMT 0 breaking, 0 notable, 0 editorial changes since v1.41.0. Semantic conventions v1.41.0 — 1 breaking, 58 notable https://semconv.com/releases/semconv/1.41.0 https://semconv.com/releases/semconv/1.41.0 Tue, 28 Apr 2026 04:57:50 GMT 1 breaking, 58 notable, 95 editorial changes since v1.40.0. BREAKING · attribute type-changed · deployment.environment.name — Type changed from `string` to `enum`. NOTABLE · metric renamed · k8s.container.cpu.limit — Renamed to `k8s.container.cpu.limit.desired`. NOTABLE · metric renamed · k8s.container.cpu.limit_utilization — Renamed to `k8s.container.cpu.limit.utilization`. NOTABLE · metric renamed · k8s.container.cpu.request — Renamed to `k8s.container.cpu.request.desired`. NOTABLE · metric renamed · k8s.container.cpu.request_utilization — Renamed to `k8s.container.cpu.request.utilization`. NOTABLE · metric renamed · k8s.container.memory.limit — Renamed to `k8s.container.memory.limit.desired`. NOTABLE · metric renamed · k8s.container.memory.request — Renamed to `k8s.container.memory.request.desired`. NOTABLE · attribute stability-changed · container.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · container.image.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · container.image.repo_digests — Promoted to release_candidate. NOTABLE · attribute stability-changed · container.image.tags — Promoted to release_candidate. NOTABLE · attribute stability-changed · deployment.environment.name — Promoted to stable. NOTABLE · signal stability-changed · entity.telemetry.distro — Promoted to stable. NOTABLE · attribute stability-changed · k8s.cluster.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.cluster.uid — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.container.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.container.restart_count — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.cronjob.annotation — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.cronjob.label — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.cronjob.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.cronjob.uid — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.daemonset.annotation — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.daemonset.label — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.daemonset.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.daemonset.uid — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.deployment.annotation — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.deployment.label — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.deployment.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.deployment.uid — Promoted to release_candidate. NOTABLE · attribute stability-changed · k8s.job.annotation — Promoted to release_candidate. …and 29 more. Specification v1.56.0 — 9 breaking, 46 notable https://semconv.com/releases/spec/1.56.0 https://semconv.com/releases/spec/1.56.0 Mon, 20 Apr 2026 16:55:43 GMT 9 breaking, 46 notable, 128 editorial changes since v1.55.0. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: The processor MUST bridge a `LogRecord` to a span event if and only if all of the following conditions are met: BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: If any of these conditions is not met, the processor MUST do nothing. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: When a `LogRecord` is bridged, the processor MUST add exactly one span event with the following mapping: BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: the span event name MUST be the `LogRecord`'s Event Name. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: if the `LogRecord` has a Timestamp set, it MUST be used as the span event timestamp. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: Otherwise, if the `LogRecord` has an ObservedTimestamp set, it MUST be used as the span event timestamp. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST added: all `LogRecord` Attributes MUST be copied to the span event as span event attributes. BREAKING · requirement requirement-added · specification/logs/sdk.md#event-to-span-event-bridge — MUST NOT added: Note that bridging a `LogRecord` to a span event MUST NOT prevent that `LogRecord` from continuing through the normal log processing pipeline. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST NOT added: If `trace_based` is `false`, log records MUST NOT be affected because of this parameter. NOTABLE · requirement requirement-removed · specification/compatibility/opentracing.md#abstract — MUST removed: This functionality MUST be defined in its own OpenTracing Shim Layer, not in the OpenTracing nor the OpenTelemetry API or SDK. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#exemplars-1 — MUST removed: Exemplars on other OpenTelemetry data points MUST be dropped. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#exemplars-1 — MUST removed: For Prometheus pull endpoints, only a single exemplar is able to be added to each bucket, so the largest exemplar from each bucket MUST be used, if attaching exemplars. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#exemplars-1 — MUST removed: If no exemplars exist on a bucket, the highest exemplar from a lower bucket MUST be used, even though it is a duplicate of another bucket's exemplar. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#exemplars-1 — MUST removed: Prometheus Exemplars MUST use the `traceid` and `spanid` keys for the trace and span IDs, respectively. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#histograms — MUST removed: Multiple Prometheus histogram metrics MUST be merged together into a single OTLP Histogram: NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1 — MUST NOT removed: Brackets MUST NOT be included in the resulting unit. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#start-time — MUST removed: When no `created` metric is available, conversion MUST follow Cumulative streams: handling unknown start time by default. NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#case-sensitivity — MUST removed: For maximum compatibility, implementations MUST: NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#name-restrictions — MUST NOT removed: MUST NOT include characters forbidden in environment variables per platform-specific restrictions NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#size-limitations — MUST removed: When truncation is required due to size limitations, implementations MUST truncate whole entries. NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#size-limitations — MUST removed: Implementers MUST document how graceful truncation is handled and SHOULD provide the link to the corresponding specification (e.g., [W3C tracestate Truncation guidance][w3c-truncation]). NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#value-restrictions — MUST removed: MUST only use characters that are valid in HTTP header fields per RFC 9110 NOTABLE · requirement requirement-removed · specification/context/env-carriers.md#value-restrictions — MUST removed: MUST follow the format requirements of the specific propagation protocol (e.g., W3C Trace Context specification for `TRACEPARENT` values) NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1 — SHOULD strengthened to MUST: The Unit of an OTLP metric point MUST be converted from the UCUM unit to the equivalent unit word in Prometheus if it is included in the table in Metric Metadata above. NOTABLE · document stability-changed · specification/compatibility/opentracing.md — Status changed from Stable to Deprecated. NOTABLE · document stability-changed · specification/context/env-carriers.md — Status changed from Alpha to Beta. NOTABLE · document stability-changed · specification/metrics/sdk_exporters/prometheus.md — Status changed from Development to Mixed. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#counters — MUST added: Exemplars on the Prometheus Counter Sample MUST be converted to OpenTelemetry Exemplars on the OpenTelemetry Sum data point following the rules in Exemplars. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#exemplar-conversion — MUST added: When an exemplar is converted per the metric-type-specific sections above, the OpenTelemetry Exemplar MUST be converted to a Prometheus exemplar if the Prometheus (push or pull) protocol being used supports them, as fol... NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#exemplar-conversion — MUST added: If present, the OpenTelemetry Exemplar's Trace ID and Span ID MUST be added as Exemplar labels using the `traceid` and `spanid` keys, respectively. …and 25 more. OTLP v1.10.0 — 0 breaking, 3 notable https://semconv.com/releases/proto/1.10.0 https://semconv.com/releases/proto/1.10.0 Mon, 09 Mar 2026 14:04:12 GMT 0 breaking, 3 notable, 2 editorial changes since v1.9.0. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.attribute_indices — Field number changed from 3 to 2. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.link_index — Field number changed from 4 to 3. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.values — Field number changed from 2 to 4. Every previously encoded message decodes wrongly. Specification v1.55.0 — 9 breaking, 11 notable https://semconv.com/releases/spec/1.55.0 https://semconv.com/releases/spec/1.55.0 Thu, 05 Mar 2026 16:26:37 GMT 9 breaking, 11 notable, 13 editorial changes since v1.54.0. BREAKING · requirement requirement-added · specification/configuration/data-model.md#environment-variable-substitution — MUST added: When `PREFIX` is absent or `env`, `GENERIC-SUBSTITUTION` MUST conform to `ENV-SUBSTITUTION`: BREAKING · requirement requirement-added · specification/trace/api.md#concurrency-requirements — MUST added: TracerProvider - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/trace/api.md#concurrency-requirements — MUST added: Tracer - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/trace/api.md#concurrency-requirements — MUST added: Span - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/trace/api.md#concurrency-requirements — MUST added: Event - Events are immutable and MUST be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/trace/sdk.md#concurrency-requirements — MUST added: Tracer Provider - Tracer creation, `ForceFlush` and `Shutdown` MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/trace/sdk.md#concurrency-requirements — MUST added: Sampler - `ShouldSample` and `GetDescription` MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/trace/sdk.md#concurrency-requirements — MUST added: Span processor - all methods MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/trace/sdk.md#concurrency-requirements — MUST added: Span Exporter - `ForceFlush` and `Shutdown` MUST be safe to be called concurrently. NOTABLE · section removed · specification/trace/api.md#concurrency — Section "Concurrency" removed. NOTABLE · document stability-changed · specification/configuration/api.md — Status changed from Development to Mixed. NOTABLE · document stability-changed · specification/configuration/data-model.md — Status changed from Development to Stable. NOTABLE · document stability-changed · specification/configuration/sdk.md — Status changed from Development to Stable. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#summaries — MUST added: In text formats where Prometheus Summaries are represented by multiple samples, samples with same metric family name MUST be merged together into a single OTLP Summary. NOTABLE · requirement requirement-added · specification/configuration/data-model.md#environment-variable-substitution — MAY added: Language implementations MAY support additional prefixes beyond `env:` to access language-specific configuration sources. NOTABLE · requirement requirement-added · specification/configuration/data-model.md#environment-variable-substitution — SHOULD added: Language implementations SHOULD document any additional prefixes they support. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#start-timestamps — MUST added: For delta aggregations, the start timestamp MUST equal the previous collection interval's timestamp, or the creation time of the instrument if this is the first collection interval for the instrument. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#start-timestamps — MUST added: This implies that all data points with delta temporality aggregation for an instrument MUST share the same start timestamp. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#start-timestamps — MUST added: Cumulative timeseries MUST use a consistent start timestamp for all collection intervals. NOTABLE · requirement requirement-added · specification/trace/api.md#concurrency-requirements — SHOULD added: Link - Links are immutable and SHOULD be safe for concurrent use by default. Semantic conventions v1.40.0 — 0 breaking, 31 notable https://semconv.com/releases/semconv/1.40.0 https://semconv.com/releases/semconv/1.40.0 Thu, 19 Feb 2026 17:50:21 GMT 0 breaking, 31 notable, 115 editorial changes since v1.39.0. NOTABLE · attribute renamed · feature_flag.evaluation.error.message — Renamed to `feature_flag.error.message`. NOTABLE · metric renamed · system.memory.shared — Renamed to `system.memory.linux.shared`. NOTABLE · attribute deprecated · error.message — Use domain-specific error message attribute. For example, use `feature_flag.error.message` for feature flag errors. NOTABLE · signal deprecated · event.rpc.message — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · message.compressed_size — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · message.id — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · message.type — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · message.uncompressed_size — Deprecated, no replacement at this time. NOTABLE · metric deprecated · rpc.client.request.size — Removed, no replacement at this time. NOTABLE · metric deprecated · rpc.client.response.size — Removed, no replacement at this time. NOTABLE · attribute deprecated · rpc.message.compressed_size — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · rpc.message.id — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · rpc.message.type — Deprecated, no replacement at this time. NOTABLE · attribute deprecated · rpc.message.uncompressed_size — Deprecated, no replacement at this time. NOTABLE · metric deprecated · rpc.server.request.size — Removed, no replacement at this time. NOTABLE · metric deprecated · rpc.server.response.size — Removed, no replacement at this time. NOTABLE · signal stability-changed · entity.service.instance — Promoted to stable. NOTABLE · signal stability-changed · entity.service.namespace — Promoted to stable. NOTABLE · metric stability-changed · rpc.client.call.duration — Promoted to release_candidate. NOTABLE · attribute stability-changed · rpc.method — Promoted to release_candidate. NOTABLE · attribute stability-changed · rpc.method_original — Promoted to release_candidate. NOTABLE · attribute stability-changed · rpc.response.status_code — Promoted to release_candidate. NOTABLE · metric stability-changed · rpc.server.call.duration — Promoted to release_candidate. NOTABLE · attribute stability-changed · rpc.system.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · service.instance.id — Promoted to stable. NOTABLE · attribute stability-changed · service.namespace — Promoted to stable. NOTABLE · signal stability-changed · span.db.oracledb.client — Promoted to release_candidate. NOTABLE · signal stability-changed · span.rpc.call.client — Promoted to release_candidate. NOTABLE · signal stability-changed · span.rpc.call.server — Promoted to release_candidate. NOTABLE · signal stability-changed · span.rpc.grpc.call.client — Promoted to release_candidate. …and 1 more. Specification v1.54.0 — 11 breaking, 34 notable https://semconv.com/releases/spec/1.54.0 https://semconv.com/releases/spec/1.54.0 Fri, 13 Feb 2026 17:12:14 GMT 11 breaking, 34 notable, 45 editorial changes since v1.53.0. BREAKING · requirement requirement-added · specification/logs/api.md#concurrency-requirements — MUST added: LoggerProvider - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/logs/api.md#concurrency-requirements — MUST added: Logger - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/logs/sdk.md#concurrency-requirements — MUST added: LoggerProvider - Logger creation, `ForceFlush` and `Shutdown` MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/logs/sdk.md#concurrency-requirements — MUST added: Logger - all methods MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/logs/sdk.md#concurrency-requirements — MUST added: LogRecordExporter - `ForceFlush` and `Shutdown` MUST be safe to be called concurrently. BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST added: Status: Development - If an Exception is provided, the SDK MUST by default set attributes from the exception on the `LogRecord` with the conventions outlined in the exception semantic conventions. BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST NOT added: User-provided attributes MUST take precedence and MUST NOT be overwritten by exception-derived attributes. BREAKING · requirement requirement-added · specification/metrics/api.md#concurrency-requirements — MUST added: MeterProvider - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/metrics/api.md#concurrency-requirements — MUST added: Meter - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/metrics/api.md#concurrency-requirements — MUST added: Instrument - all methods MUST be documented that implementations need to be safe for concurrent use by default. BREAKING · requirement requirement-added · specification/resource/sdk.md#specifying-resource-information-via-an-environment-variable — MUST added: The `,` and `=` characters in keys and values MUST be percent encoded. NOTABLE · requirement requirement-removed · specification/configuration/sdk.md#componentsprovider-operations — MUST removed: The `ComponentsProvider` MUST provide the following functions: NOTABLE · requirement requirement-removed · specification/configuration/sdk.md#register-componentprovider — MUST removed: The SDK MUST provide a mechanism to register `ComponentProvider`. NOTABLE · requirement requirement-level-changed · specification/configuration/api.md#get-instrumentation-config — MUST relaxed to SHOULD: If the `.instrumentation` node is not set, get instrumentation config SHOULD return an empty `ConfigProperties` (as if `.instrumentation: {}` was set). NOTABLE · document stability-changed · specification/compatibility/prometheus_and_openmetrics.md — Status changed from Development to Mixed. NOTABLE · requirement requirement-added · specification/common/README.md#anyvalue-representation-for-non-otlp-protocols — SHOULD added: For protocols that do not natively support some of the AnyValue types, those values SHOULD be represented as strings following the encoding rules below. NOTABLE · requirement requirement-added · specification/common/README.md#arrays — SHOULD added: Arrays, except for byte arrays, SHOULD be represented as JSON arrays. NOTABLE · requirement requirement-added · specification/common/README.md#arrays — SHOULD added: Nested byte arrays SHOULD be represented as Base64-encoded JSON strings. NOTABLE · requirement requirement-added · specification/common/README.md#arrays — SHOULD added: Nested empty values SHOULD be represented as JSON null. NOTABLE · requirement requirement-added · specification/common/README.md#arrays — SHOULD added: The special floating point values NaN and Infinity SHOULD be represented as JSON strings `"NaN"`, `"Infinity"`, and `"-Infinity"`. NOTABLE · requirement requirement-added · specification/common/README.md#booleans — SHOULD added: Booleans SHOULD be represented as JSON booleans. NOTABLE · requirement requirement-added · specification/common/README.md#byte-arrays — SHOULD added: Byte arrays SHOULD be Base64-encoded. NOTABLE · requirement requirement-added · specification/common/README.md#byte-arrays — SHOULD NOT added: They SHOULD NOT be encoded as JSON strings (with explicit surrounding quotes). NOTABLE · requirement requirement-added · specification/common/README.md#empty-values — SHOULD added: Empty values SHOULD be represented as the empty string. NOTABLE · requirement requirement-added · specification/common/README.md#empty-values — SHOULD NOT added: They SHOULD NOT be encoded as a JSON string (with explicit surrounding quotes). NOTABLE · requirement requirement-added · specification/common/README.md#floating-point-numbers — SHOULD added: Floating point numbers SHOULD be represented as JSON numbers. NOTABLE · requirement requirement-added · specification/common/README.md#floating-point-numbers — SHOULD added: The special floating point values NaN and Infinity SHOULD be represented as `NaN`, `Infinity`, and `-Infinity`. NOTABLE · requirement requirement-added · specification/common/README.md#floating-point-numbers — SHOULD NOT added: They SHOULD NOT be encoded as JSON strings (with explicit surrounding quotes). NOTABLE · requirement requirement-added · specification/common/README.md#integers — SHOULD added: Integers SHOULD be represented as JSON numbers. NOTABLE · requirement requirement-added · specification/common/README.md#maps — SHOULD added: Maps SHOULD be represented as JSON objects. …and 15 more. Semantic conventions v1.39.0 — 0 breaking, 31 notable https://semconv.com/releases/semconv/1.39.0 https://semconv.com/releases/semconv/1.39.0 Mon, 12 Jan 2026 22:11:41 GMT 0 breaking, 31 notable, 134 editorial changes since v1.38.0. NOTABLE · signal removed · span.rpc.client — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.connect_rpc.client — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.connect_rpc.server — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.grpc.client — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.grpc.server — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.jsonrpc.client — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.jsonrpc.server — Removed from the registry (was development). NOTABLE · signal removed · span.rpc.server — Removed from the registry (was development). NOTABLE · attribute renamed · linux.memory.slab.state — Renamed to `system.memory.linux.slab.state`. NOTABLE · attribute renamed · peer.service — Renamed to `service.peer.name`. NOTABLE · metric renamed · process.open_file_descriptor.count — Renamed to `process.unix.file_descriptor.count`. NOTABLE · attribute renamed · rpc.connect_rpc.error_code — Renamed to `rpc.response.status_code`. NOTABLE · attribute renamed · rpc.connect_rpc.request.metadata — Renamed to `rpc.request.metadata`. NOTABLE · attribute renamed · rpc.connect_rpc.response.metadata — Renamed to `rpc.response.metadata`. NOTABLE · attribute renamed · rpc.grpc.request.metadata — Renamed to `rpc.request.metadata`. NOTABLE · attribute renamed · rpc.grpc.response.metadata — Renamed to `rpc.response.metadata`. NOTABLE · attribute renamed · rpc.jsonrpc.request_id — Renamed to `jsonrpc.request.id`. NOTABLE · attribute renamed · rpc.jsonrpc.version — Renamed to `jsonrpc.protocol.version`. NOTABLE · attribute renamed · rpc.system — Renamed to `rpc.system.name`. NOTABLE · metric renamed · system.linux.memory.available — Renamed to `system.memory.linux.available`. NOTABLE · metric renamed · system.linux.memory.slab.usage — Renamed to `system.memory.linux.slab.usage`. NOTABLE · metric deprecated · rpc.client.duration — Replaced by `rpc.client.call.duration` with unit `s`. NOTABLE · attribute deprecated · rpc.grpc.status_code — Use string representation of the gRPC status code on the `rpc.response.status_code` attribute. NOTABLE · attribute deprecated · rpc.jsonrpc.error_code — Use string representation of the error code on the `rpc.response.status_code` attribute. NOTABLE · attribute deprecated · rpc.jsonrpc.error_message — Use the span status description or `error.message` attribute on other signals. NOTABLE · metric deprecated · rpc.server.duration — Replaced by `rpc.server.call.duration` with unit `s`. NOTABLE · attribute deprecated · rpc.service — Value should be included in `rpc.method` which is expected to be a fully-qualified name. NOTABLE · metric unit-changed · system.linux.memory.available — Unit changed from `By` to `{packet}`. NOTABLE · metric unit-changed · system.linux.memory.slab.usage — Unit changed from `By` to `{packet}`. NOTABLE · metric instrument-changed · system.linux.memory.available — Instrument changed from `updowncounter` to `counter`. …and 1 more. Specification v1.53.0 — 2 breaking, 7 notable https://semconv.com/releases/spec/1.53.0 https://semconv.com/releases/spec/1.53.0 Fri, 09 Jan 2026 17:00:08 GMT 2 breaking, 7 notable, 13 editorial changes since v1.52.0. BREAKING · requirement requirement-removed · specification/logs/data-model.md#type-mapstring-any — MUST removed: The implementation MUST by default ensure that the exported maps contain only unique keys. BREAKING · requirement requirement-removed · specification/logs/data-model.md#type-mapstring-any — MUST removed: If such option is provided, it MUST be documented that for many receivers, handling of maps with duplicate keys is unpredictable and it is the users' responsibility to ensure keys are not duplicate. NOTABLE · section removed · specification/logs/data-model.md#definitions-used-in-this-document — Section "Definitions Used in this Document" removed. NOTABLE · section removed · specification/logs/data-model.md#type-any — Section "Type `any`" removed. NOTABLE · section removed · specification/logs/data-model.md#type-mapstring-any — Section "Type `map<string, any>`" removed. NOTABLE · requirement requirement-level-changed · specification/configuration/sdk.md#create — SHOULD strengthened to MUST: If a property is required, and not present, Create MUST return an error. NOTABLE · requirement requirement-added · specification/logs/api.md#ergonomic-api — MAY added: Languages MAY additionally provide a more ergonomic and convenient logging API. NOTABLE · requirement requirement-added · specification/logs/api.md#ergonomic-api — SHOULD added: The ergonomic API SHOULD make it more convenient to emit event records following the event semantics. NOTABLE · requirement requirement-added · specification/logs/api.md#ergonomic-api — SHOULD added: The design of the ergonomic API SHOULD be idiomatic for its language. Specification v1.52.0 — 12 breaking, 19 notable https://semconv.com/releases/spec/1.52.0 https://semconv.com/releases/spec/1.52.0 Fri, 12 Dec 2025 17:20:16 GMT 12 breaking, 19 notable, 29 editorial changes since v1.51.0. BREAKING · requirement requirement-removed · specification/configuration/sdk-environment-variables.md#duration — MUST removed: Any value that represents a duration MUST be an integer representing a number of milliseconds. BREAKING · requirement requirement-removed · specification/configuration/sdk-environment-variables.md#duration — MUST removed: The value is non-negative - if a negative value is provided, the implementation MUST generate a warning, gracefully ignore the setting and use the default value if it is defined. BREAKING · requirement requirement-removed · specification/configuration/sdk-environment-variables.md#enum — MUST removed: If a null object (empty, no-op) value is acceptable, then the enum value representing it MUST be `"none"`. BREAKING · requirement requirement-removed · specification/configuration/sdk-environment-variables.md#timeout — MUST removed: Any value that represents a timeout MUST be an integer representing a number of milliseconds. BREAKING · requirement requirement-removed · specification/configuration/sdk-environment-variables.md#timeout — MUST removed: The value is non-negative - if a negative value is provided, the implementation MUST generate a warning, gracefully ignore the setting and use the default value if it is defined. BREAKING · requirement requirement-added · specification/configuration/common.md#duration — MUST added: Any value that represents a duration MUST be an integer representing a number of milliseconds. BREAKING · requirement requirement-added · specification/configuration/common.md#duration — MUST added: The value is non-negative - if a negative value is provided, the implementation MUST generate a warning, gracefully ignore the setting and use the default value if it is defined. BREAKING · requirement requirement-added · specification/configuration/common.md#enum — MUST added: If a null object (empty, no-op) value is acceptable, then the enum value representing it MUST be `"none"`. BREAKING · requirement requirement-added · specification/configuration/common.md#numeric — MUST added: > The following paragraph was added after stabilization and the requirements are > thus qualified as "SHOULD" to allow implementations to avoid breaking changes. > For new > implementations, these should be treated as M... BREAKING · requirement requirement-added · specification/configuration/common.md#timeout — MUST added: Any value that represents a timeout MUST be an integer representing a number of milliseconds. BREAKING · requirement requirement-added · specification/configuration/common.md#timeout — MUST added: The value is non-negative - if a negative value is provided, the implementation MUST generate a warning, gracefully ignore the setting and use the default value if it is defined. BREAKING · requirement requirement-added · specification/trace/sdk.md#alwaysrecord — MUST added: Based on the decision from the wrapped root sampler, `AlwaysRecord` MUST behave as follows: NOTABLE · section removed · specification/configuration/sdk-environment-variables.md#configuration-types — Section "Configuration types" removed. NOTABLE · section removed · specification/configuration/sdk-environment-variables.md#duration — Section "Duration" removed. NOTABLE · section removed · specification/configuration/sdk-environment-variables.md#integer — Section "Integer" removed. NOTABLE · section removed · specification/configuration/sdk-environment-variables.md#timeout — Section "Timeout" removed. NOTABLE · requirement requirement-level-changed · specification/metrics/sdk.md#instrument-enabled — MUST relaxed to SHOULD: Otherwise, it SHOULD return `true`. NOTABLE · document stability-changed · specification/trace/sdk_exporters/zipkin.md — Status changed from Stable to Deprecated. NOTABLE · requirement requirement-added · specification/configuration/common.md#enum — MAY added: For configuration sources which accept a known value out of a set, i.e., an enum value, implementations MAY support additional values not listed here. NOTABLE · requirement requirement-added · specification/configuration/common.md#enum — SHOULD added: When reporting configuration errors, implementations SHOULD display the original user-provided value to aid debugging. NOTABLE · requirement requirement-added · specification/configuration/common.md#integer — SHOULD added: If an implementation chooses to support an integer-valued configuration source, it SHOULD support non-negative values between 0 and 2³¹ − 1 (inclusive). NOTABLE · requirement requirement-added · specification/configuration/common.md#integer — MAY added: Individual SDKs MAY choose to support a larger range of values. NOTABLE · requirement requirement-added · specification/configuration/common.md#numeric — SHOULD added: For sources accepting a numeric value, if the user provides a value which is outside the valid range for the configuration item, the implementation SHOULD generate a warning and gracefully ignore the setting, i.e., trea... NOTABLE · requirement requirement-added · specification/configuration/common.md#numeric — SHOULD NOT added: In particular, implementations SHOULD NOT assign a custom interpretation e.g. to negative values if a negative value does not naturally apply to a configuration and does not have an explicitly specified meaning, but tre... NOTABLE · requirement requirement-added · specification/configuration/common.md#opentelemetry-common-configuration-specification — MAY added: Implementations MAY choose to allow configuration via any configuration source in this specification, but are not required to. NOTABLE · requirement requirement-added · specification/configuration/common.md#opentelemetry-common-configuration-specification — SHOULD added: If they do, they SHOULD follow the guidance listed in this document. NOTABLE · requirement requirement-added · specification/configuration/common.md#timeout — SHOULD added: Implementations SHOULD interpret timeout zero values (i.e. `0` indicating 0 milliseconds) as no limit (i.e. infinite). NOTABLE · requirement requirement-added · specification/configuration/common.md#timeout — MAY added: In practice, implementations MAY treat no limit as "a very long time" and substitute a very large duration ( e.g. the maximum milliseconds representable by a 32-bit integer). NOTABLE · requirement requirement-added · specification/configuration/sdk-environment-variables.md#opentelemetry-environment-variable-specification — SHOULD added: They SHOULD also follow the common configuration specification. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-enabled — MUST added: The instrument `Enabled` MUST return `false` when either: …and 1 more. Specification v1.51.0 — 10 breaking, 5 notable https://semconv.com/releases/spec/1.51.0 https://semconv.com/releases/spec/1.51.0 Mon, 17 Nov 2025 14:18:03 GMT 10 breaking, 5 notable, 30 editorial changes since v1.50.0. BREAKING · requirement requirement-removed · specification/common/README.md#attribute-collections — MUST NOT removed: The keys in each such collection are unique, i.e. there MUST NOT exist more than one key-value pair with the same key. BREAKING · requirement requirement-removed · specification/logs/data-model.md#field-attributes — MUST removed: The log attribute model MUST support `any` type, a superset of standard Attribute, to preserve the semantics of structured attributes emitted by the applications. BREAKING · requirement requirement-added · specification/common/README.md#attribute — MUST added: The attribute value MUST be one of types defined in AnyValue. BREAKING · requirement requirement-added · specification/common/README.md#attribute-collections — MUST added: Implementation MUST by default enforce that the exported attribute collections contain only unique keys. BREAKING · requirement requirement-added · specification/common/README.md#attribute-collections — MUST added: If such option is provided, it MUST be documented that for many receivers, handling of maps with duplicate keys is unpredictable and it is the users' responsibility to ensure keys are not duplicate. BREAKING · requirement requirement-added · specification/common/README.md#attribute-limits — MUST added: Status: Development - if it is a byte array, if its length exceeds that limit (counting each byte as 1), SDKs MUST truncate that value, so that its length is at most equal to the limit, BREAKING · requirement requirement-added · specification/common/README.md#attribute-limits — MUST NOT added: otherwise an attribute MUST NOT be discarded. BREAKING · requirement requirement-added · specification/common/README.md#mapstring-anyvalue — MUST added: Case sensitivity of keys MUST be preserved. BREAKING · requirement requirement-added · specification/common/README.md#mapstring-anyvalue — MUST added: The implementation MUST by default enforce that the exported maps contain only unique keys. BREAKING · requirement requirement-added · specification/common/README.md#mapstring-anyvalue — MUST added: If such option is provided, it MUST be documented that for many receivers, handling of maps with duplicate keys is unpredictable and it is the users' responsibility to ensure keys are not duplicate. NOTABLE · section removed · specification/common/README.md#standard-attribute — Section "Standard Attribute" removed. NOTABLE · requirement requirement-added · specification/common/README.md#anyvalue — SHOULD added: APIs SHOULD be documented in a way to communicate to users that using array and map values may carry higher performance overhead compared to primitive values. NOTABLE · requirement requirement-added · specification/common/README.md#anyvalue — SHOULD added: While `null` is a valid attribute value, its use within homogeneous arrays SHOULD generally be avoided unless language constraints make this impossible. NOTABLE · requirement requirement-added · specification/common/README.md#attribute-collections — MAY added: Implementations MAY have an option to allow exporting attribute collections with duplicate keys (e.g. for better performance). NOTABLE · requirement requirement-added · specification/common/README.md#mapstring-anyvalue — MAY added: The implementation MAY have an option to allow exporting maps with duplicate keys (e.g. for better performance). OTLP v1.9.0 — 0 breaking, 10 notable https://semconv.com/releases/proto/1.9.0 https://semconv.com/releases/proto/1.9.0 Fri, 31 Oct 2025 19:13:47 GMT 0 breaking, 10 notable, 0 editorial changes since v1.8.0. NOTABLE · message removed · opentelemetry.proto.profiles.v1development.AggregationTemporality — enum removed from opentelemetry/proto/profiles/v1development/profiles.proto. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.comment_strindices — Field 7 (`int32`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ValueType.aggregation_temporality — Field 3 (`AggregationTemporality`) removed. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.attribute_indices — Field number changed from 12 to 11. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.dropped_attributes_count — Field number changed from 9 to 8. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload — Field number changed from 11 to 10. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload_format — Field number changed from 10 to 9. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.profile_id — Field number changed from 8 to 7. Every previously encoded message decodes wrongly. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Location.line — Renamed to `lines` (field 3 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Profile.sample — Renamed to `samples` (field 2 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. Semantic conventions v1.38.0 — 0 breaking, 48 notable https://semconv.com/releases/semconv/1.38.0 https://semconv.com/releases/semconv/1.38.0 Wed, 29 Oct 2025 20:23:26 GMT 0 breaking, 48 notable, 208 editorial changes since v1.37.0. NOTABLE · metric renamed · k8s.cronjob.active_jobs — Renamed to `k8s.cronjob.job.active`. NOTABLE · metric renamed · k8s.daemonset.current_scheduled_nodes — Renamed to `k8s.daemonset.node.current_scheduled`. NOTABLE · metric renamed · k8s.daemonset.desired_scheduled_nodes — Renamed to `k8s.daemonset.node.desired_scheduled`. NOTABLE · metric renamed · k8s.daemonset.misscheduled_nodes — Renamed to `k8s.daemonset.node.misscheduled`. NOTABLE · metric renamed · k8s.daemonset.ready_nodes — Renamed to `k8s.daemonset.node.ready`. NOTABLE · metric renamed · k8s.deployment.available_pods — Renamed to `k8s.deployment.pod.available`. NOTABLE · metric renamed · k8s.deployment.desired_pods — Renamed to `k8s.deployment.pod.desired`. NOTABLE · metric renamed · k8s.hpa.current_pods — Renamed to `k8s.hpa.pod.current`. NOTABLE · metric renamed · k8s.hpa.desired_pods — Renamed to `k8s.hpa.pod.desired`. NOTABLE · metric renamed · k8s.hpa.max_pods — Renamed to `k8s.hpa.pod.max`. NOTABLE · metric renamed · k8s.hpa.min_pods — Renamed to `k8s.hpa.pod.min`. NOTABLE · metric renamed · k8s.job.active_pods — Renamed to `k8s.job.pod.active`. NOTABLE · metric renamed · k8s.job.desired_successful_pods — Renamed to `k8s.job.pod.desired_successful`. NOTABLE · metric renamed · k8s.job.failed_pods — Renamed to `k8s.job.pod.failed`. NOTABLE · metric renamed · k8s.job.max_parallel_pods — Renamed to `k8s.job.pod.max_parallel`. NOTABLE · metric renamed · k8s.job.successful_pods — Renamed to `k8s.job.pod.successful`. NOTABLE · metric renamed · k8s.node.allocatable.cpu — Renamed to `k8s.node.cpu.allocatable`. NOTABLE · metric renamed · k8s.node.allocatable.ephemeral_storage — Renamed to `k8s.node.ephemeral_storage.allocatable`. NOTABLE · metric renamed · k8s.node.allocatable.memory — Renamed to `k8s.node.memory.allocatable`. NOTABLE · metric renamed · k8s.node.allocatable.pods — Renamed to `k8s.node.pod.allocatable`. NOTABLE · metric renamed · k8s.replicaset.available_pods — Renamed to `k8s.replicaset.pod.available`. NOTABLE · metric renamed · k8s.replicaset.desired_pods — Renamed to `k8s.replicaset.pod.desired`. NOTABLE · metric renamed · k8s.replication_controller.available_pods — Renamed to `k8s.replicationcontroller.pod.available`. NOTABLE · metric renamed · k8s.replication_controller.desired_pods — Renamed to `k8s.replicationcontroller.pod.desired`. NOTABLE · metric renamed · k8s.replicationcontroller.available_pods — Renamed to `k8s.replicationcontroller.pod.available`. NOTABLE · metric renamed · k8s.replicationcontroller.desired_pods — Renamed to `k8s.replicationcontroller.pod.desired`. NOTABLE · metric renamed · k8s.statefulset.current_pods — Renamed to `k8s.statefulset.pod.current`. NOTABLE · metric renamed · k8s.statefulset.desired_pods — Renamed to `k8s.statefulset.pod.desired`. NOTABLE · metric renamed · k8s.statefulset.ready_pods — Renamed to `k8s.statefulset.pod.ready`. NOTABLE · metric renamed · k8s.statefulset.updated_pods — Renamed to `k8s.statefulset.pod.updated`. …and 18 more. Specification v1.50.0 — 15 breaking, 26 notable https://semconv.com/releases/spec/1.50.0 https://semconv.com/releases/spec/1.50.0 Fri, 17 Oct 2025 14:46:40 GMT 15 breaking, 26 notable, 24 editorial changes since v1.49.0. BREAKING · requirement requirement-removed · specification/logs/sdk.md#loggerconfig — MUST removed: The value of `disabled` MUST be used to resolve whether a `Logger` is Enabled. BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST added: Status: Development Before processing a log record, the implementation MUST apply the filtering rules defined by the LoggerConfig (in case `Enabled` was not called prior to emitting the record): BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST added: Minimum severity: If the log record's SeverityNumber is specified (i.e. not `0`) and is less than the configured `minimum_severity`, the log record MUST be dropped. BREAKING · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — MUST added: Trace-based: If `trace_based` is `true`, and if the log record has a `SpanId` and the `TraceFlags` SAMPLED flag is unset, the log record MUST be dropped. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST added: If not explicitly set, the `minimum_severity` parameter MUST default to `0`. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST added: If a log record's SeverityNumber is specified (i.e. not `0`) and is less than the configured `minimum_severity`, the log record MUST be dropped by the `Logger`. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST added: If not explicitly set, the `trace_based` parameter MUST default to `false`. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST added: If `trace_based` is `true`, log records associated with unsampled traces MUST be dropped by the `Logger`. BREAKING · requirement requirement-added · specification/logs/sdk.md#loggerconfig — MUST added: However, the changes MUST be eventually visible. BREAKING · requirement requirement-added · specification/trace/sdk.md#probabilitysampler — MUST added: The `ProbabilitySampler` sampler MUST ignore the parent `SampledFlag`. BREAKING · requirement requirement-added · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST added: The sampling algorithm MUST be deterministic. BREAKING · requirement requirement-added · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST added: A trace identified by a given `TraceId` is sampled or not independent of language, time, etc. To achieve this, implementations MUST use a deterministic hash of the `TraceId` when computing the sampling decision. BREAKING · requirement requirement-added · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST added: A `TraceIdRatioBased` sampler with a given sampling probability MUST also sample all traces that any `TraceIdRatioBased` sampler with a lower sampling probability would sample. BREAKING · requirement requirement-added · specification/trace/sdk.md#traceidratiobased — SHALL NOT added: OpenTelemetry SDK implementors SHALL NOT remove or modify the behavior of the original `TraceIdRatioBased` sampler until at least January 1, BREAKING · requirement requirement-added · specification/trace/sdk.md#tracerconfig — MUST added: However, the changes MUST be eventually visible. NOTABLE · section removed · specification/trace/sdk.md#composabletraceidratiobased — Section "ComposableTraceIDRatioBased" removed. NOTABLE · section removed · specification/trace/sdk.md#traceidratiobased-sampler-algorithm — Section "`TraceIdRatioBased` sampler algorithm" removed. NOTABLE · section removed · specification/trace/sdk.md#traceidratiobased-sampler-compatibility-warning — Section "`TraceIdRatioBased` sampler compatibility warning" removed. NOTABLE · section removed · specification/trace/sdk.md#traceidratiobased-sampler-configuration — Section "`TraceIdRatioBased` sampler configuration" removed. NOTABLE · section removed · specification/trace/sdk.md#traceidratiobased-sampler-description — Section "`TraceIdRatioBased` sampler description" removed. NOTABLE · document removed · specification/trace/tracestate-probability-sampling-experimental.md — Document removed (was Development). NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-combine-multiple-consistent-probability-samplers-using-the-minimum-p-value — MUST removed: When combining Sampler decisions for multiple consistent probability Samplers and at least one decides to sample, the minimum of the "yes" decision `p` values MUST be set in the `tracestate`. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-combining-multiple-sampling-decisions-using-logical-or — MUST removed: When multiple samplers are combined using composition, the sampling decision MUST be to sample if at least one of the combined samplers decides to sample. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-consistentprobabilitybased-sampler-decides-not-to-sample-for-probabilities-less-than-2-62 — MUST removed: If the configured sampling probability is in the interval `[0, 2**-62)`, the Sampler MUST decide not to sample. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-consistentprobabilitybased-sampler-records-unbiased-adjusted-counts — MUST removed: The `ConsistentProbabilityBased` Sampler with non-zero probability MUST set `p` so that the adjusted count interpreted from the `tracestate` is an unbiased estimate of the number of representative spans in the populatio... NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-consistentprobabilitybased-sampler-sets-p-when-sampled — MUST removed: The `ConsistentProbabilityBased` Sampler MUST set `p` when it decides to sample according to its configured sampling probability. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-consistentprobabilitybased-sampler-sets-r-for-root-span — MUST removed: The `ConsistentProbabilityBased` Sampler MUST set `r` when it makes a root sampling decision. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-consistentprobabilitybased-sampler-unsets-p-when-not-sampled — MUST removed: The `ConsistentProbabilityBased` Sampler MUST unset `p` from the `tracestate` when it decides not to sample. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-parentconsistentprobabilitybased-calls-the-configured-root-sampler-for-root-spans — MUST removed: The `ParentConsistentProbabilityBased` Sampler MUST delegate to the configured root Sampler when there is not a valid parent trace context. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling-experimental.md#requirement-parentconsistentprobabilitybased-does-not-modify-valid-tracestate — MUST NOT removed: The `ParentConsistentProbabilityBased` Sampler MUST NOT modify a valid `tracestate`. …and 11 more. Specification v1.49.0 — 0 breaking, 9 notable https://semconv.com/releases/spec/1.49.0 https://semconv.com/releases/spec/1.49.0 Tue, 16 Sep 2025 17:42:30 GMT 0 breaking, 9 notable, 14 editorial changes since v1.48.0. NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#character-encoding — MUST added: All attribute values MUST be considered strings and characters outside the `baggage-octet` range MUST be percent-encoded following the W3C Baggage specification. NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#character-encoding — MUST added: The reserved characters `{}[]@;,=` MUST be percent-encoded when they appear literally in attribute values: NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#specifying-entity-information-via-an-environment-variable — MUST added: The SDK that has access to environment variables MUST provide an `EnvEntityDetector` which will use the `OTEL_ENTITIES` environment variable to discover and associate defined entities with the resource. NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#validation-requirements — MUST NOT added: Entity type MUST NOT be empty and MUST match the pattern `[a-zA-Z][a-zA-Z0-9.-]` NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#validation-requirements — MUST added: At least one identifying attribute MUST be present in the `{...}` block NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#validation-requirements — MUST NOT added: Attribute keys MUST NOT be empty and SHOULD follow OpenTelemetry semantic conventions NOTABLE · requirement requirement-added · specification/entities/entity-propagation.md#validation-requirements — MUST added: Schema URL, if present, MUST be a valid URI NOTABLE · requirement requirement-added · specification/protocol/exporter.md#user-agent — MAY added: Exporters MAY expose a configuration option to add a product identifier to the User-Agent header. NOTABLE · requirement requirement-added · specification/protocol/exporter.md#user-agent — SHOULD added: The resulting User-Agent SHOULD include the exporter's default User-Agent string. OTLP v1.8.0 — 0 breaking, 33 notable https://semconv.com/releases/proto/1.8.0 https://semconv.com/releases/proto/1.8.0 Tue, 02 Sep 2025 15:06:17 GMT 0 breaking, 33 notable, 2 editorial changes since v1.7.0. NOTABLE · message removed · opentelemetry.proto.profiles.v1development.AttributeUnit — message removed from opentelemetry/proto/profiles/v1development/profiles.proto. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Location.is_folded — Field 4 (`bool`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Mapping.has_filenames — Field 7 (`bool`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Mapping.has_functions — Field 6 (`bool`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Mapping.has_inline_frames — Field 9 (`bool`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Mapping.has_line_numbers — Field 8 (`bool`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.default_sample_type_index — Field 9 (`int32`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.duration_nanos — Field 5 (`int64`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Sample.value — Field 3 (`int64`) removed. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Location.attribute_indices — Field number changed from 5 to 4. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.attribute_indices — Field number changed from 14 to 12. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.comment_strindices — Field number changed from 8 to 7. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.dropped_attributes_count — Field number changed from 11 to 9. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload — Field number changed from 13 to 11. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload_format — Field number changed from 12 to 10. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.period — Field number changed from 7 to 6. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.period_type — Field number changed from 6 to 5. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.profile_id — Field number changed from 10 to 8. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.attribute_indices — Field number changed from 4 to 3. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.link_index — Field number changed from 5 to 4. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Sample.timestamps_unix_nano — Field number changed from 6 to 5. Every previously encoded message decodes wrongly. NOTABLE · field field-type-changed · opentelemetry.proto.profiles.v1development.ProfilesDictionary.attribute_table — Type changed from `opentelemetry.proto.common.v1.KeyValue` to `KeyValueAndUnit`. NOTABLE · field field-type-changed · opentelemetry.proto.profiles.v1development.Sample.timestamps_unix_nano — Type changed from `uint64` to `fixed64`. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Profile.location_indices — Renamed to `time_unix_nano` (field 3 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Profile.time_nanos — Renamed to `duration_nano` (field 4 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.ProfilesDictionary.attribute_units — Renamed to `stack_table` (field 7 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Sample.locations_length — Renamed to `values` (field 2 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Sample.locations_start_index — Renamed to `stack_index` (field 1 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. NOTABLE · field field-label-changed · opentelemetry.proto.profiles.v1development.Location.mapping_index — Cardinality changed from `optional` to `singular`. NOTABLE · field field-label-changed · opentelemetry.proto.profiles.v1development.Profile.sample_type — Cardinality changed from `repeated` to `singular`. …and 3 more. Semantic conventions v1.37.0 — 0 breaking, 17 notable https://semconv.com/releases/semconv/1.37.0 https://semconv.com/releases/semconv/1.37.0 Mon, 25 Aug 2025 23:38:36 GMT 0 breaking, 17 notable, 285 editorial changes since v1.36.0. NOTABLE · signal removed · span.gen_ai.azure.ai.inference.client — Removed from the registry (was development). NOTABLE · signal removed · span.gen_ai.openai.inference.client — Removed from the registry (was development). NOTABLE · metric removed · system.network.dropped — Removed from the registry (was development). NOTABLE · metric removed · system.network.packets — Removed from the registry (was development). NOTABLE · attribute renamed · android.state — Renamed to `android.app.state`. NOTABLE · attribute renamed · container.runtime — Renamed to `container.runtime.name`. NOTABLE · attribute renamed · enduser.role — Renamed to `user.roles`. NOTABLE · attribute renamed · gen_ai.openai.request.service_tier — Renamed to `openai.request.service_tier`. NOTABLE · attribute renamed · gen_ai.openai.response.service_tier — Renamed to `openai.response.service_tier`. NOTABLE · attribute renamed · gen_ai.openai.response.system_fingerprint — Renamed to `openai.response.system_fingerprint`. NOTABLE · attribute renamed · gen_ai.system — Renamed to `gen_ai.provider.name`. NOTABLE · attribute renamed · ios.state — Renamed to `ios.app.state`. NOTABLE · signal deprecated · event.gen_ai.assistant.message — Chat history is reported on `gen_ai.input.messages` attribute on spans or `gen_ai.client.inference.operation.details` event. NOTABLE · signal deprecated · event.gen_ai.choice — Chat history is reported on `gen_ai.output.messages` attribute on spans or `gen_ai.client.inference.operation.details` event. NOTABLE · signal deprecated · event.gen_ai.system.message — Chat history is reported on `gen_ai.system_instructions` attribute on spans or `gen_ai.client.inference.operation.details` event. NOTABLE · signal deprecated · event.gen_ai.tool.message — Chat history is reported on `gen_ai.input.messages` attribute on spans or `gen_ai.client.inference.operation.details` event. NOTABLE · signal deprecated · event.gen_ai.user.message — Chat history is reported on `gen_ai.input.messages` attribute on spans or `gen_ai.client.inference.operation.details` event. Specification v1.48.0 — 0 breaking, 21 notable https://semconv.com/releases/spec/1.48.0 https://semconv.com/releases/spec/1.48.0 Wed, 13 Aug 2025 15:51:44 GMT 0 breaking, 21 notable, 14 editorial changes since v1.47.0. NOTABLE · requirement requirement-removed · specification/metrics/sdk_exporters/prometheus.md#configuration — MUST removed: The option MAY be named `without_units`, and MUST be `false` by default. NOTABLE · requirement requirement-removed · specification/metrics/sdk_exporters/prometheus.md#configuration — MUST removed: The option MAY be named `withouttypesuffix`, and MUST be `false` by default. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-attributes — MUST relaxed to SHOULD: Discouraged characters SHOULD be replace with the `` character. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-attributes — MUST relaxed to SHOULD: Multiple consecutive `` characters SHOULD be replaced with a single `` character. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1 — MUST relaxed to SHOULD: Discouraged characters in the metric name SHOULD be replaced with the `` character by default, aiming for compatibility with Prometheus conventions. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1 — MUST relaxed to SHOULD: Multiple consecutive `` characters SHOULD be replaced with a single `_` character. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1 — MUST relaxed to SHOULD: The resulting unit SHOULD be added to the metric as UNIT metadata. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope-1 — MUST added: Scope attributes with names 'name', 'version', or 'schemaurl' MUST be dropped to avoid conflicts with the already existing `otelscopename`, `otelscopeversion`, and `otelscopeschema_url` labels. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#native-histograms — MUST added: A Prometheus Native Histogram with standard (exponential) schema (i.e. schemas -4 to 8) and which are of the integer and counter flavor MUST be converted to an OTLP Exponential Histogram as follows: NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#native-histograms — MUST added: Native histograms of the float or gauge flavors MUST be dropped. NOTABLE · requirement requirement-added · specification/compatibility/prometheus_and_openmetrics.md#native-histograms — MUST added: Native Histograms with `Schema` outside of the range [-4, 8] MUST be dropped. NOTABLE · requirement requirement-added · specification/configuration/sdk-environment-variables.md#enum — SHOULD added: Enum values SHOULD be interpreted in a case-insensitive manner. NOTABLE · requirement requirement-added · specification/configuration/sdk-environment-variables.md#enum — SHOULD added: When reporting configuration errors, implementations SHOULD display the original user-provided value to aid debugging. NOTABLE · requirement requirement-added · specification/logs/data-model.md#comparing-severity — MAY added: Special handling MAY be given to `SeverityNumber=0` when it is used to represent an unspecified severity. NOTABLE · requirement requirement-added · specification/logs/sdk.md#onemit — OPTIONAL added: However, it is OPTIONAL for `ReadWriteLogRecord` to be concurrent-safe. NOTABLE · requirement requirement-added · specification/logs/sdk.md#onemit — SHOULD added: To avoid such race conditions, implementations SHOULD recommended to users that a clone of `logRecord` be used for any concurrent processing, such as in a batching processor. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#configuration — MUST added: If the Prometheus exporter supports such configuration it MUST be named to something that resembles Prometheus configuration option `translation_strategy`, and the translation options MUST be: NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST added: Although a Prometheus Exporter MAY be configured with a `translation_strategy` for internal metric processing, the final output format and character escaping MUST follow what the content negotiation process determines b... NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST added: The content negotiation requirements MUST take precedence over the configured translation strategy when determining the final output format. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#interaction-with-translation-strategy — MUST added: If configured with `NoTranslation` but the client requests `escaping=underscores`, the exporter MUST apply underscore escaping. NOTABLE · requirement requirement-added · specification/protocol/exporter.md#configuration-options — SHOULD added: [4]: The default protocol SHOULD be `http/protobuf`, unless there are strong reasons for SDKs to select `grpc` as the default. Specification v1.47.0 — 4 breaking, 16 notable https://semconv.com/releases/spec/1.47.0 https://semconv.com/releases/spec/1.47.0 Fri, 18 Jul 2025 15:53:09 GMT 4 breaking, 16 notable, 50 editorial changes since v1.46.0. BREAKING · requirement requirement-added · specification/trace/sdk.md#enabled — MUST added: `Enabled` MUST return `false` when either: BREAKING · requirement requirement-added · specification/trace/sdk.md#getsamplingintent — MUST NOT added: Note: ComposableSamplers MUST NOT modify the parameters passed to delegate GetSamplingIntent methods, as they are considered read-only state. BREAKING · requirement requirement-added · specification/trace/sdk.md#getsamplingintent — MUST NOT added: ComposableSamplers MUST NOT modify the OpenTelemetry TraceState (i.e., the `ot` sub-key of TraceState). BREAKING · requirement requirement-added · specification/trace/sdk.md#getsamplingintent — MUST added: The calling CompositeSampler SHOULD update the threshold of the outgoing TraceState (unless `!threshold_reliable`) and that the explicit randomness values MUST not be modified. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#consistent-sampling-decision-approach — MUST removed: If the current sampling stage applies a greater threshold value than any stage before, it MUST update (increase) the threshold correspondingly by re-encoding the OpenTelemetry TraceState value. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#downstream-samplers — MUST NOT removed: If the chosen sampling probability is 1, the sampler MUST NOT modify an existing `th` sub-key value, nor set a `th` sub-key value. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#downstream-samplers — MUST removed: In this case the sampler MUST output the span with a `th` equal to `max(input th, chosen th)`. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#downstream-samplers — MUST NOT removed: In other words, `th` MUST NOT be decreased (as it is not possible to retroactively adjust an earlier stage's sampling probability), and it MUST be increased if a lower sampling probability was used. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#head-samplers — MUST removed: The `th` key MUST be defined with a threshold value corresponding to the sampling probability the sampler used. NOTABLE · requirement requirement-removed · specification/trace/tracestate-probability-sampling.md#head-samplers — MUST removed: If trace randomness was derived from a OpenTelemetry TraceState `rv` sub-key value, the same `rv` value MUST be defined and equal to the incoming OpenTelemetry TraceState `rv` sub-key value. NOTABLE · document stability-changed · specification/context/env-carriers.md — Status changed from Experimental to Alpha. NOTABLE · requirement requirement-added · specification/context/env-carriers.md#process-spawning — MUST NOT added: The language implementations MUST NOT handle spawning processes. NOTABLE · requirement requirement-added · specification/document-status.md#maturity-levels — MUST added: They also MUST communicate in which version they will be removed.| |Unmaintained |A component identified as unmaintained does not have an active code owner. NOTABLE · requirement requirement-added · specification/logs/data-model.md#field-severitynumber — MAY added: `SeverityNumber=0` MAY be used to represent an unspecified value. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#content-negotiation — MUST added: A Prometheus Exporter MUST support content negotiation to allow clients to request metrics in different formats based on the `Accept` header in HTTP requests. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/prometheus.md#content-negotiation — MUST added: Content negotiation MUST follow Prometheus Content Negotiation guidelines. NOTABLE · requirement requirement-added · specification/trace/sdk.md#composabletraceidratiobased — SHOULD added: For the zero case a `ComposableAlwaysOff` instance SHOULD be returned instead. NOTABLE · requirement requirement-added · specification/trace/sdk.md#enabled — SHOULD added: Otherwise, it SHOULD return `true`. NOTABLE · requirement requirement-added · specification/trace/sdk.md#enabled — MAY added: It MAY return `false` to support additional optimizations and features. NOTABLE · requirement requirement-added · specification/trace/sdk.md#getsamplingintent — MAY added: Parent context, threshold, incoming trace state, and trace flag information MAY be precomputed so that ComposableSamplers do not repeatedly probe the Context for this information. Semantic conventions v1.36.0 — 0 breaking, 2 notable https://semconv.com/releases/semconv/1.36.0 https://semconv.com/releases/semconv/1.36.0 Sat, 05 Jul 2025 16:55:46 GMT 0 breaking, 2 notable, 5 editorial changes since v1.35.0. NOTABLE · metric deprecated · otel.sdk.span.ended — Deprecated (obsoleted). NOTABLE · metric deprecated · otel.sdk.span.ended.count — Deprecated (obsoleted). Semantic conventions v1.35.0 — 0 breaking, 23 notable https://semconv.com/releases/semconv/1.35.0 https://semconv.com/releases/semconv/1.35.0 Mon, 30 Jun 2025 20:02:16 GMT 0 breaking, 23 notable, 130 editorial changes since v1.34.0. NOTABLE · signal removed · span.gen_ai.az.ai.inference.client — Removed from the registry (was development). NOTABLE · attribute renamed · az.namespace — Renamed to `azure.resource_provider.namespace`. NOTABLE · attribute renamed · az.service_request_id — Renamed to `azure.service.request.id`. NOTABLE · metric renamed · cpu.frequency — Renamed to `system.cpu.frequency`. NOTABLE · metric renamed · cpu.time — Renamed to `system.cpu.time`. NOTABLE · metric renamed · cpu.utilization — Renamed to `system.cpu.utilization`. NOTABLE · signal renamed · event.az.resource.log — Renamed to `azure.resource.log`. NOTABLE · metric renamed · system.network.connections — Renamed to `system.network.connection.count`. NOTABLE · signal deprecated · entity.otel.scope — Deprecated (obsoleted). NOTABLE · metric unit-changed · cpu.frequency — Unit changed from `Hz` to `{Hz}`. NOTABLE · metric unit-changed · system.cpu.frequency — Unit changed from `{Hz}` to `Hz`. NOTABLE · signal stability-changed · event.feature_flag.evaluation — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.context.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.key — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.provider.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.result.reason — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.result.value — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.result.variant — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.set.id — Promoted to release_candidate. NOTABLE · attribute stability-changed · feature_flag.version — Promoted to release_candidate. NOTABLE · metric undeprecated · system.cpu.frequency — No longer marked deprecated. NOTABLE · metric undeprecated · system.cpu.time — No longer marked deprecated. NOTABLE · metric undeprecated · system.cpu.utilization — No longer marked deprecated. Specification v1.46.0 — 0 breaking, 12 notable https://semconv.com/releases/spec/1.46.0 https://semconv.com/releases/spec/1.46.0 Thu, 12 Jun 2025 14:48:48 GMT 0 breaking, 12 notable, 17 editorial changes since v1.45.0. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope — MUST removed: Labels on `otelscopeinfo` metric points other than `otelscopename` and `otelscopeversion`, MUST be added as scope attributes to the scope with the matching name and version. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope-1 — MUST removed: Scope attributes MUST also be added as labels following the rules described in the `Metric Attributes` section below. NOTABLE · requirement requirement-removed · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope-1 — MUST removed: Prometheus exporters MUST add the scope name as the `otelscopename` label and the scope version as the `otelscopeversion` label on all metric points by default, based on the scope the original data point was nested in. NOTABLE · requirement requirement-level-changed · specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope — SHOULD strengthened to MUST: Labels with `otelscope` prefix MUST be dropped from all metric points and used as the Instrumentation Scope name (`otelscopename`), version (`otelscopeversion`), schema URL (`otelscopeschemaurl`), at... NOTABLE · requirement requirement-added · specification/common/instrumentation-scope.md#instrumentation-scope — SHOULD added: This tuple SHOULD uniquely identify the logical unit of software that emits the telemetry. NOTABLE · requirement requirement-added · specification/common/instrumentation-scope.md#instrumentation-scope — SHOULD added: The instrumentation scope's name SHOULD be specified to identify the `InstrumentationScope` name. NOTABLE · requirement requirement-added · specification/common/instrumentation-scope.md#instrumentation-scope — SHOULD added: The instrumentation scope's optional Schema URL SHOULD identify the Telemetry Schema that the instrumentation's emitted telemetry conforms to. NOTABLE · requirement requirement-added · specification/entities/data-model.md#identifying-attributes — MUST added: OpenTelemetry Semantic Conventions MUST define a set of identifying attribute keys for every defined entity type. NOTABLE · requirement requirement-added · specification/entities/data-model.md#identifying-attributes — MUST added: Two independent observers that report the same entity MUST be able to supply identical values for all identifying attributes. NOTABLE · requirement requirement-added · specification/entities/data-model.md#identifying-attributes — MUST NOT added: If an observer cannot reliably obtain one or more identifying attributes, it MUST NOT emit telemetry using that entity type. NOTABLE · requirement requirement-added · specification/entities/data-model.md#placement-of-shared-descriptive-attributes — MUST added: If multiple entities share the same descriptive attribute key with potentially conflicting values, the attribute MUST logically belong to only one of them. NOTABLE · requirement requirement-added · specification/entities/data-model.md#placement-of-shared-descriptive-attributes — MUST added: The attribute MUST be referenced by the most specific entity, the one closest in the topology graph to the entity associated with the telemetry signal. OTLP v1.7.0 — 0 breaking, 7 notable https://semconv.com/releases/proto/1.7.0 https://semconv.com/releases/proto/1.7.0 Wed, 21 May 2025 13:38:43 GMT 0 breaking, 7 notable, 2 editorial changes since v1.6.0. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.attribute_table — Field 7 (`opentelemetry.proto.common.v1.KeyValue`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.attribute_units — Field 8 (`AttributeUnit`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.function_table — Field 4 (`Function`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.link_table — Field 5 (`Link`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.location_table — Field 3 (`Location`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.ProfilesData.string_table — Field 6 (`string`) removed. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.ProfilesData.mapping_table — Renamed to `dictionary` (field 2 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. Semantic conventions v1.34.0 — 1 breaking, 126 notable https://semconv.com/releases/semconv/1.34.0 https://semconv.com/releases/semconv/1.34.0 Mon, 19 May 2025 19:48:21 GMT 1 breaking, 126 notable, 90 editorial changes since v1.33.0. BREAKING · attribute deprecated · exception.escaped — It's no longer recommended to record exceptions that are handled and do not escape the scope of a span. NOTABLE · attribute renamed · code.column — Renamed to `code.column.number`. NOTABLE · attribute renamed · code.filepath — Renamed to `code.file.path`. NOTABLE · attribute renamed · code.lineno — Renamed to `code.line.number`. NOTABLE · attribute renamed · container.cpu.state — Renamed to `cpu.mode`. NOTABLE · attribute renamed · container.labels — Renamed to `container.label`. NOTABLE · attribute renamed · db.cassandra.consistency_level — Renamed to `cassandra.consistency.level`. NOTABLE · attribute renamed · db.cassandra.coordinator.dc — Renamed to `cassandra.coordinator.dc`. NOTABLE · attribute renamed · db.cassandra.coordinator.id — Renamed to `cassandra.coordinator.id`. NOTABLE · attribute renamed · db.cassandra.idempotence — Renamed to `cassandra.query.idempotent`. NOTABLE · attribute renamed · db.cassandra.page_size — Renamed to `cassandra.page.size`. NOTABLE · attribute renamed · db.cassandra.speculative_execution_count — Renamed to `cassandra.speculative_execution.count`. NOTABLE · attribute renamed · db.cassandra.table — Renamed to `db.collection.name`. NOTABLE · metric renamed · db.client.connections.idle.max — Renamed to `db.client.connection.idle.max`. NOTABLE · metric renamed · db.client.connections.idle.min — Renamed to `db.client.connection.idle.min`. NOTABLE · metric renamed · db.client.connections.max — Renamed to `db.client.connection.max`. NOTABLE · metric renamed · db.client.connections.pending_requests — Renamed to `db.client.connection.pending_requests`. NOTABLE · attribute renamed · db.client.connections.pool.name — Renamed to `db.client.connection.pool.name`. NOTABLE · attribute renamed · db.client.connections.state — Renamed to `db.client.connection.state`. NOTABLE · metric renamed · db.client.connections.timeouts — Renamed to `db.client.connection.timeouts`. NOTABLE · metric renamed · db.client.connections.usage — Renamed to `db.client.connection.count`. NOTABLE · metric renamed · db.client.cosmosdb.active_instance.count — Renamed to `azure.cosmosdb.client.active_instance.count`. NOTABLE · metric renamed · db.client.cosmosdb.operation.request_charge — Renamed to `azure.cosmosdb.client.operation.request_charge`. NOTABLE · attribute renamed · db.cosmosdb.client_id — Renamed to `azure.client.id`. NOTABLE · attribute renamed · db.cosmosdb.connection_mode — Renamed to `azure.cosmosdb.connection.mode`. NOTABLE · attribute renamed · db.cosmosdb.consistency_level — Renamed to `azure.cosmosdb.consistency.level`. NOTABLE · attribute renamed · db.cosmosdb.container — Renamed to `db.collection.name`. NOTABLE · attribute renamed · db.cosmosdb.regions_contacted — Renamed to `azure.cosmosdb.operation.contacted_regions`. NOTABLE · attribute renamed · db.cosmosdb.request_charge — Renamed to `azure.cosmosdb.operation.request_charge`. NOTABLE · attribute renamed · db.cosmosdb.request_content_length — Renamed to `azure.cosmosdb.request.body.size`. …and 97 more. Specification v1.45.0 — 0 breaking, 7 notable https://semconv.com/releases/spec/1.45.0 https://semconv.com/releases/spec/1.45.0 Wed, 14 May 2025 15:51:13 GMT 0 breaking, 7 notable, 7 editorial changes since v1.44.0. NOTABLE · requirement requirement-added · specification/logs/sdk.md#emit-a-logrecord — SHOULD added: If Observed Timestamp is unspecified, the implementation SHOULD set it equal to the current time. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: Resource detectors SHOULD have a unique name for reference in configuration. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: Names SHOULD be snake case and consist of lowercase alphanumeric and `_` characters, which ensures they conform to declarative configuration property name requirements. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: Resource detector names SHOULD reflect the root namespace of attributes they populate. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: Resource detectors which populate attributes from multiple root namespaces SHOULD choose a name which appropriately conveys their purpose. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: An SDK which identifies multiple resource detectors with the same name SHOULD report an error. NOTABLE · requirement requirement-added · specification/resource/sdk.md#resource-detector-name — SHOULD added: In order to limit collisions, resource detectors SHOULD document their name in a manner which is easily discoverable. Semantic conventions v1.33.0 — 2 breaking, 33 notable https://semconv.com/releases/semconv/1.33.0 https://semconv.com/releases/semconv/1.33.0 Fri, 02 May 2025 19:48:40 GMT 2 breaking, 33 notable, 139 editorial changes since v1.32.0. BREAKING · attribute stability-changed · db.operation.parameter — Stability lowered to development. BREAKING · attribute stability-changed · db.system — Stability lowered to development. NOTABLE · signal removed · span.db.mssql.client — Removed from the registry (was development). NOTABLE · signal removed · span.gen_ai.client — Removed from the registry (was development). NOTABLE · signal removed · span.gen_ai.openai.client — Removed from the registry (was development). NOTABLE · attribute deprecated · feature_flag.evaluation.error.message — Replaced by `error.message`. NOTABLE · attribute deprecated · feature_flag.provider_name — Replaced by `feature_flag.provider.name`. NOTABLE · metric deprecated · otel.sdk.exporter.span.exported.count — Renamed to `otel.sdk.exporter.span.exported`. NOTABLE · metric deprecated · otel.sdk.exporter.span.inflight.count — Renamed to `otel.sdk.exporter.span.inflight`. NOTABLE · metric deprecated · otel.sdk.processor.span.processed.count — Renamed to `otel.sdk.processor.span.processed`. NOTABLE · metric deprecated · otel.sdk.span.ended.count — Renamed to `otel.sdk.span.ended`. NOTABLE · metric deprecated · otel.sdk.span.live.count — Renamed to `otel.sdk.span.live`. NOTABLE · metric instrument-changed · otel.sdk.exporter.span.exported.count — Instrument changed from `counter` to `updowncounter`. NOTABLE · metric instrument-changed · otel.sdk.processor.span.processed.count — Instrument changed from `counter` to `updowncounter`. NOTABLE · attribute stability-changed · code.column.number — Promoted to stable. NOTABLE · attribute stability-changed · code.file.path — Promoted to stable. NOTABLE · attribute stability-changed · code.function.name — Promoted to stable. NOTABLE · attribute stability-changed · code.line.number — Promoted to stable. NOTABLE · attribute stability-changed · code.stacktrace — Promoted to stable. NOTABLE · metric stability-changed · db.client.operation.duration — Promoted to stable. NOTABLE · attribute stability-changed · db.collection.name — Promoted to stable. NOTABLE · attribute stability-changed · db.namespace — Promoted to stable. NOTABLE · attribute stability-changed · db.operation.batch.size — Promoted to stable. NOTABLE · attribute stability-changed · db.operation.name — Promoted to stable. NOTABLE · attribute stability-changed · db.query.summary — Promoted to stable. NOTABLE · attribute stability-changed · db.query.text — Promoted to stable. NOTABLE · attribute stability-changed · db.response.status_code — Promoted to stable. NOTABLE · attribute stability-changed · db.stored_procedure.name — Promoted to stable. NOTABLE · attribute stability-changed · db.system.name — Promoted to stable. NOTABLE · signal stability-changed · span.db.client — Promoted to stable. …and 5 more. OTLP v1.6.0 — 0 breaking, 19 notable https://semconv.com/releases/proto/1.6.0 https://semconv.com/releases/proto/1.6.0 Tue, 29 Apr 2025 11:43:12 GMT 0 breaking, 19 notable, 15 editorial changes since v1.5.0. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.attribute_table — Field 7 (`opentelemetry.proto.common.v1.KeyValue`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.attribute_units — Field 8 (`AttributeUnit`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.default_sample_type_strindex — Field 16 (`int32`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.function_table — Field 6 (`Function`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.location_table — Field 4 (`Location`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.mapping_table — Field 3 (`Mapping`) removed. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.string_table — Field 10 (`string`) removed. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.attribute_indices — Field number changed from 22 to 14. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.comment_strindices — Field number changed from 15 to 8. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.dropped_attributes_count — Field number changed from 19 to 11. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.duration_nanos — Field number changed from 12 to 5. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.location_indices — Field number changed from 5 to 3. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload — Field number changed from 21 to 13. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.original_payload_format — Field number changed from 20 to 12. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.period — Field number changed from 14 to 7. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.period_type — Field number changed from 13 to 6. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.profile_id — Field number changed from 17 to 10. Every previously encoded message decodes wrongly. NOTABLE · field field-number-changed · opentelemetry.proto.profiles.v1development.Profile.time_nanos — Field number changed from 11 to 4. Every previously encoded message decodes wrongly. NOTABLE · field field-renamed · opentelemetry.proto.profiles.v1development.Profile.link_table — Renamed to `default_sample_type_index` (field 9 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name. Specification v1.44.0 — 4 breaking, 31 notable https://semconv.com/releases/spec/1.44.0 https://semconv.com/releases/spec/1.44.0 Tue, 15 Apr 2025 14:54:08 GMT 4 breaking, 31 notable, 75 editorial changes since v1.43.0. BREAKING · requirement requirement-removed · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST removed: The sampling algorithm MUST be deterministic. BREAKING · requirement requirement-removed · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST removed: A trace identified by a given `TraceId` is sampled or not independent of language, time, etc. To achieve this, implementations MUST use a deterministic hash of the `TraceId` when computing the sampling decision. BREAKING · requirement requirement-removed · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — MUST removed: A `TraceIdRatioBased` sampler with a given sampling rate MUST also sample all traces that any `TraceIdRatioBased` sampler with a lower sampling rate would sample. BREAKING · requirement requirement-added · specification/logs/sdk.md#enabled-1 — MUST NOT added: Any modifications to parameters inside `Enabled` MUST NOT be propagated to the caller. NOTABLE · document removed · specification/project-management.md — Document removed (was Unspecified). NOTABLE · section removed · specification/trace/sdk.md#do-not-overwrite-explicit-trace-randomness — Section "Do not overwrite explicit trace randomness" removed. NOTABLE · section removed · specification/trace/sdk.md#explicit-trace-randomness — Section "Explicit trace randomness" removed. NOTABLE · section removed · specification/trace/sdk.md#requirements-for-traceidratiobased-sampler-algorithm — Section "Requirements for `TraceIdRatioBased` sampler algorithm" removed. NOTABLE · section removed · specification/trace/sdk.md#root-samplers-set-explicit-trace-randomness-for-non-random-traceids — Section "Root samplers set explicit trace randomness for non-random TraceIDs" removed. NOTABLE · requirement requirement-removed · specification/configuration/data-model.md#environment-variable-substitution — MUST removed: The `ENVNAME` MUST start with an alphabetic or `` character, and is followed by 0 or more alphanumeric or `_` characters. NOTABLE · requirement requirement-removed · specification/configuration/data-model.md#environment-variable-substitution — MUST removed: When parsing a configuration file that contains a reference not matching the references regular expression but does match the following PCRE2 regular expression, the parser MUST return an empty result (no partial result... NOTABLE · requirement requirement-level-changed · specification/metrics/sdk.md#measurement-processing — SHOULD strengthened to MUST: If it is not possible to apply the View without producing semantic errors (e.g. the View sets an asynchronous instrument to use the Explicit bucket histogram aggregation) the implementation SHOULD em... NOTABLE · requirement requirement-added · specification/context/env-carriers.md#case-sensitivity — MUST added: For maximum compatibility, implementations MUST: NOTABLE · requirement requirement-added · specification/context/env-carriers.md#name-restrictions — MUST NOT added: MUST NOT include characters forbidden in environment variables per platform-specific restrictions NOTABLE · requirement requirement-added · specification/context/env-carriers.md#size-limitations — MUST added: When truncation is required due to size limitations, implementations MUST truncate whole entries. NOTABLE · requirement requirement-added · specification/context/env-carriers.md#size-limitations — MUST added: Implementers MUST document how graceful truncation is handled and SHOULD provide the link to the corresponding specification (e.g., [W3C tracestate Truncation guidance][w3c-truncation]). NOTABLE · requirement requirement-added · specification/context/env-carriers.md#value-restrictions — MUST added: MUST only use characters that are valid in HTTP header fields per RFC 9110 NOTABLE · requirement requirement-added · specification/context/env-carriers.md#value-restrictions — MUST added: MUST follow the format requirements of the specific propagation protocol (e.g., W3C Trace Context specification for `TRACEPARENT` values) NOTABLE · requirement requirement-added · specification/entities/data-model.md#entity-data-model — MUST added: MUST not change during the lifetime of the entity. NOTABLE · requirement requirement-added · specification/entities/data-model.md#entity-data-model — MUST added: This field is required and MUST not be empty for valid entities. </td> </tr> <tr> <td>Id </td> <td>map&lt;string, standard attribute value&gt; </td> <td>Attributes that identify the entity. <p> MUST not change during th... NOTABLE · requirement requirement-added · specification/logs/sdk.md#enabled-1 — MAY added: `Enabled` is an operation that a `LogRecordProcessor` MAY implement in order to support filtering via `Logger.Enabled`. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-advisory-parameter-explicitbucketboundaries — MUST added: If no View matches, or if a matching View selects the default aggregation, the `ExplicitBucketBoundaries` advisory parameter MUST be used. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#instrument-advisory-parameters — MUST added: If both a View and advisory parameters specify the same aspect of the Stream configuration, the setting defined by the View MUST take precedence over the advisory parameters. NOTABLE · requirement requirement-added · specification/metrics/sdk.md#measurement-processing — MUST added: Instrument advisory parameters, if any, MUST be honored. NOTABLE · requirement requirement-added · specification/resource/data-model.md#resource-data-model — MUST added: <table> <tr> <td><strong>Field</strong> </td> <td><strong>Type</strong> </td> <td><strong>Description</strong> </td> </tr> <tr> <td>Entities </td> <td>set&lt;Entity&gt; </td> <td>Defines the set of Entities associated w... NOTABLE · requirement requirement-added · specification/resource/README.md#overview — MUST added: It MUST identify an entity that is producing telemetry. NOTABLE · requirement requirement-added · specification/trace/sdk.md#traceidratiobased-sampler-algorithm — SHOULD added: When (R >= T), the OpenTelemetry TraceState SHOULD be modified to include the key-value `th:T` for rejection threshold value (T), as specified for the [OpenTelemetry TraceState `th` sub-key][TRACESTATEHANDLING]. NOTABLE · requirement requirement-added · specification/trace/sdk.md#traceidratiobased-sampler-compatibility-warning — SHOULD added: When a TraceIdRatioBased Sampler makes a decision for a non-root Span using TraceID randomness, but the Trace random flag was not set, the SDK SHOULD issue a warning statement in its log with a compatibility warning. NOTABLE · requirement requirement-added · specification/trace/tracestate-probability-sampling.md#consistent-sampling-decision-approach — MUST added: For this, two values MUST be present in the `SpanContext`: NOTABLE · requirement requirement-added · specification/trace/tracestate-probability-sampling.md#consistent-sampling-decision-approach — MUST added: If the current sampling stage applies a greater threshold value than any stage before, it MUST update (increase) the threshold correspondingly by re-encoding the OpenTelemetry TraceState value. …and 5 more. Semantic conventions v1.32.0 — 0 breaking, 2 notable https://semconv.com/releases/semconv/1.32.0 https://semconv.com/releases/semconv/1.32.0 Mon, 31 Mar 2025 16:00:23 GMT 0 breaking, 2 notable, 37 editorial changes since v1.31.0. NOTABLE · attribute deprecated · feature_flag.evaluation.reason — Replaced by `feature_flag.result.reason`. NOTABLE · attribute deprecated · feature_flag.variant — Replaced by `feature_flag.result.variant`. Specification v1.43.0 — 0 breaking, 3 notable https://semconv.com/releases/spec/1.43.0 https://semconv.com/releases/spec/1.43.0 Tue, 18 Mar 2025 12:18:47 GMT 0 breaking, 3 notable, 9 editorial changes since v1.42.0. NOTABLE · requirement requirement-added · specification/logs/sdk_exporters/stdout.md#logs-exporter---standard-output — SHOULD added: Documentation SHOULD warn users about this. NOTABLE · requirement requirement-added · specification/metrics/sdk_exporters/stdout.md#metrics-exporter---standard-output — SHOULD added: Documentation SHOULD warn users about this. NOTABLE · requirement requirement-added · specification/trace/sdk_exporters/stdout.md#span-exporter---standard-output — SHOULD added: Documentation SHOULD warn users about this. Semantic conventions v1.31.0 — 0 breaking, 24 notable https://semconv.com/releases/semconv/1.31.0 https://semconv.com/releases/semconv/1.31.0 Tue, 11 Mar 2025 00:53:13 GMT 0 breaking, 24 notable, 860 editorial changes since v1.30.0. NOTABLE · signal removed · span.aws.lambda — Removed from the registry (was experimental). NOTABLE · signal removed · span.faas — Removed from the registry (was experimental). NOTABLE · signal removed · span.faas.datasource — Removed from the registry (was experimental). NOTABLE · signal removed · span.faas.timer — Removed from the registry (was experimental). NOTABLE · signal removed · span.messaging — Removed from the registry (was experimental). NOTABLE · signal removed · span.rpc.connect_rpc — Removed from the registry (was experimental). NOTABLE · signal removed · span.rpc.grpc — Removed from the registry (was experimental). NOTABLE · signal removed · span.rpc.jsonrpc — Removed from the registry (was experimental). NOTABLE · attribute deprecated · code.filepath — Replaced by `code.file.path` NOTABLE · attribute deprecated · code.namespace — Value should be included in `code.function.name` which is expected to be a fully-qualified name. NOTABLE · attribute deprecated · gen_ai.openai.request.response_format — Replaced by `gen_ai.output.type`. NOTABLE · metric deprecated · k8s.replication_controller.available_pods — Replaced by `k8s.replicationcontroller.available_pods`. NOTABLE · metric deprecated · k8s.replication_controller.desired_pods — Replaced by `k8s.replicationcontroller.desired_pods`. NOTABLE · metric deprecated · system.cpu.frequency — Replaced by `cpu.frequency`. NOTABLE · metric deprecated · system.cpu.time — Replaced by `cpu.time`. NOTABLE · metric deprecated · system.cpu.utilization — Replaced by `cpu.utilization`. NOTABLE · metric unit-changed · process.context_switches — Unit changed from `{count}` to `{context_switch}`. NOTABLE · metric unit-changed · process.open_file_descriptor.count — Unit changed from `{count}` to `{file_descriptor}`. NOTABLE · attribute stability-changed · code.column.number — Promoted to release_candidate. NOTABLE · attribute stability-changed · code.file.path — Promoted to release_candidate. NOTABLE · attribute stability-changed · code.function.name — Promoted to release_candidate. NOTABLE · attribute stability-changed · code.line.number — Promoted to release_candidate. NOTABLE · attribute stability-changed · code.stacktrace — Promoted to release_candidate. NOTABLE · attribute undeprecated · enduser.id — No longer marked deprecated. OTLP v1.5.0 — 0 breaking, 2 notable https://semconv.com/releases/proto/1.5.0 https://semconv.com/releases/proto/1.5.0 Tue, 17 Dec 2024 03:59:10 GMT 0 breaking, 2 notable, 2 editorial changes since v1.4.0. NOTABLE · message removed · opentelemetry.proto.profiles.v1development.Label — message removed from opentelemetry/proto/profiles/v1development/profiles.proto. NOTABLE · field field-removed · opentelemetry.proto.profiles.v1development.Profile.attributes — Field 18 (`opentelemetry.proto.common.v1.KeyValue`) removed.