OpenTelemetry Changelog https://changelog.opentelemetry.io Latest changes across OpenTelemetry repositories en-US <![CDATA[2026.03]]> https://changelog.opentelemetry.io/entry/306934176 306934176 Tue, 31 Mar 2026 10:20:17 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2026.02...2026.03

]]> <![CDATA[v1.10.0]]> https://changelog.opentelemetry.io/entry/294719488 294719488 Mon, 09 Mar 2026 14:02:36 GMT What's Changed

Added

  • profiles: introduce reference based attributes #733

Changed

  • docs: Add more clarity to experiments. #771
  • profiles: clarify Sample message usage guidance docs. #742
  • profiles: improve Sample message clarity and usage documentation. #724
  • profiles: clarify the profile and sample timestamps relationship. #744
  • common: rename ref suffix to strindex #768

Fixed

  • examples: Represent uint64 and fixed64 fields as strings in metrics.json. #748
  • logs: SEVERITY_NUMBER_UNSPECIFIED can be used as the severity_number field is optional. #736

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-proto/compare/v1.9.0...v1.10.0

]]> <![CDATA[Release 1.55.0]]> https://changelog.opentelemetry.io/entry/293584451 293584451 Thu, 05 Mar 2026 15:43:06 GMT Traces
  • Add normative language to the Tracing API/SDK spec concurrency requirements. (#4887)

Metrics

  • Add additional in-development requirements to metric start timestamps. (#4807, #4902)

Logs

  • Stabilize optional Exception parameter to Logger Emit. (#4858)

Compatibility

  • Stabilize Prometheus Summary to OTLP Summary transformation. (#4872)

SDK Configuration

  • Declarative configuration: allow language-specific prefixes in environment variable substitution. (#4891)
  • Mark significant portions of declarative configuration as stable. (#4568)
]]> <![CDATA[2026.02]]> https://changelog.opentelemetry.io/entry/296086450 296086450 Sat, 28 Feb 2026 19:18:02 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2026.01...2026.02

]]> <![CDATA[v1.40.0]]> https://changelog.opentelemetry.io/entry/288344011 288344011 Thu, 19 Feb 2026 16:57:52 GMT 🛑 Breaking changes 🛑
  • db: Oracle's db.namespace updated to represent only the database’s unique identifier. Information previously bundled into db.namespace —including PDB name, instance name, and service name — has been moved to dedicated attributes: oracle.db.pdb, oracle.db.instance.name, and oracle.db.service. Introduced a new oracle.db.domain attribute to capture the database domain (DB_DOMAIN). (#2147)
  • error, feature-flags: Deprecate error.message in favor of using domain-specific codes such as feature_flag.error.message. (#3307, #3308)
  • rpc: Remove network.protocol.name, network.protocol.version, and network.transport attributes from RPC spans and metrics. (#3349, #3350)
  • system: Rename system.memory.shared to system.memory.linux.shared (#3260) The system.memory.shared metric has been renamed to system.memory.linux.shared to align with other Linux-specific memory metrics (system.memory.linux.available and system.memory.linux.slab.usage). This metric reports shared memory used, primarily by tmpfs, and is only available on Linux systems.

🚩 Deprecations 🚩

  • exceptions: Update exception recording guidelines to not use span events. (#3256)
  • rpc: Deprecate experimental rpc.server.request.size, rpc.server.response.size, rpc.client.request.size, and rpc.client.response.size metrics due to ambiguous definitions and inconsistent implementation. (#3267)
  • rpc: Deprecate the rpc.message event and its attributes (#3266, #3283) Per-message events within RPC streaming calls are of limited utility in their current form. They are recorded as span events (also being deprecated). There is no direct replacement at this time.

💡 Enhancements 💡

  • cloud: Add oracle_cloud.realm vendor-specific attribute for Oracle Cloud Infrastructure (OCI) realm identifier. (#3121) An Oracle Cloud realm is a logical collection of cloud regions that are isolated from each other, used for compliance and data residency requirements.

  • db: Mark the Oracle Database client span as Release Candidate. (#2989)

  • db: Modify area to oracledb from oracle (#3316)

  • db: Clarified db.query.summary behavior for batch operations. (#3287)

  • db, rpc: Define domain-specific exception events for database and RPC (#3426) These domain-specific exception events provide a structured way to record exceptions that occur during operations in each area:

    • db.client.operation.exception for database client operations
    • rpc.client.call.exception and rpc.server.call.exception for RPC

  • docs: Add how-to guide for defining spans (#3240)

  • event: Allow event body to represent a display message. (#3343)

  • exception: Indicate that exception.message attribute may contain sensitive information. (#2967, #3310)

  • exceptions: Introduce OTEL_SEMCONV_EXCEPTION_SIGNAL_OPT_IN environment variable for transitioning exception recording from span events to logs. (#3363)

  • gcp: Add GCP GCE Instance Group Manager attributes (#905)

  • gen-ai: Add retrieval span support to the gen-ai semantic conventions. (#2907)

  • gen-ai: Enhance how tool calls are captured to extend support for server side tools. (#2585)

  • gen-ai: Add gen_ai.agent.version attribute to capture the version of an agent. (#3428)

  • gen-ai: Add cache token attributes and provider-specific normalization guidance for GenAI usage metrics (#1959)

    • Add gen_ai.usage.cache_read.input_tokens attribute for tokens served from provider cache
    • Add gen_ai.usage.cache_creation.input_tokens attribute for tokens written to provider cache
    • Add provider-specific token handling notes to OpenAI span
    • Add Anthropic span with computation guidance for gen_ai.usage.input_tokens

  • gen_ai: Added sampling-relevant flag to relevant GenAI span attributes to indicate their importance for sampling decisions. (#2994)

  • http: Defined declarative configuration for overriding known HTTP methods. (#3394)

  • http: Define declarative configuration for sensitive query parameters. (#3403)

  • http: Define http.client.request.exception and http.server.request.exception events for recording exceptions during HTTP operations (#3414) These domain-specific exception events provide a structured way to record exceptions that occur during HTTP client requests (network failures, timeouts) and HTTP server request processing (application errors, internal failures).

  • jvm: Add jvm.file_descriptor.limit as an in-development metric to track the maximum number of open file descriptors as reported by the JVM. (#3430)

  • k8s: Promote a selection of k8s and container attributes to beta (#3120)

  • k8s: Add k8s.service entity with endpoint and load balancer ingress metrics (#3294) New metrics:

    • k8s.service.endpoint.count: Number of endpoints by condition, address type, and zone
    • k8s.service.load_balancer.ingress.count: Number of load balancer ingress points New attributes:
    • k8s.service.endpoint.condition, k8s.service.endpoint.address_type, k8s.service.endpoint.zone
    • k8s.service.traffic_distribution, k8s.service.publish_not_ready_addresses New entity:
    • entity.k8s.service: k8s service entity with identifying and descriptive attributes

  • openai: Add openai.api.type attribute to distinguish between different OpenAI API types for similar operations. (#3337)

  • pprof: add pprof.scope.default_sample_type and pprof.scope.sample_type_order attributes to support lossless conversion of pprof profiles. (#3078)

  • rpc: Mark core RPC (plus gRPC and Apache Dubbo) semantic conventions as release candidate. (#3446)

  • rpc: Add Metrics sections to JSON-RPC, gRPC, and Connect RPC system-specific conventions (#3319, #3320)

  • rpc: Change rpc.server.call.duration and rpc.client.call.duration metrics from recommended to required (#3284)

  • rpc: Add RPC migration guide documenting changes from v1.37.0 to latest version. (#3204)

  • rpc: Clarify that network.peer.address should indicate the last contacted address in case of retries. (#3392, #3427)

  • rpc: Add semantic conventions for Apache Dubbo RPC system. (#3291)

  • rpc: Clarify how to populate server.address and server.port when using client-side load balancing or service discovery. (#3258, #3317)

  • service: Add service.criticality attribute to classify services based on operational importance (#2986) This attribute enables observability platforms to implement criticality-aware tracing, monitoring, and sampling strategies. Supports four levels: critical, high, medium, and low.

  • service: Stabilize service.instance.id attribute. (#1519) The service.instance.id attribute and entity are promoted from development to stable.

  • service: Stabilize service.namespace attribute. (#3254) The service.namespace attribute is promoted from development to stable.

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.39.0...v1.40.0

]]> <![CDATA[Release 1.54.0]]> https://changelog.opentelemetry.io/entry/286173310 286173310 Fri, 13 Feb 2026 17:08:07 GMT Context
  • Deprecate Jaeger propagator and make propagator implementation optional. (#4827)
  • Deprecate OT Trace propagator and make propagator implementation optional. (#4851)

Metrics

  • Add normative language to the Metrics API/SDK spec concurrency requirements. (#4868)

Logs

  • Add optional Exception parameter to Emit LogRecord. (#4824)
  • Add normative language to the Logging API/SDK spec concurrency requirements. (#4885)

Resource

  • Refine the handling of OTEL_RESOURCE_ATTRIBUTES. (#4856)

Common

  • Add string representation guidance for complex attribute value types (byte arrays, empty values, arrays, and maps) for non-OTLP protocols. (#4848)

Compatibility

  • Stabilize Prometheus Counter to OTLP Sum transformation. (#4862)
  • Stabilize Prometheus Gauge to OTLP Gauge transformation. (#4871)

SDK Configuration

  • Swap Tracer/Meter/LoggerConfig disabled for enabled to avoid double negatives (#4823)
  • Declarative configuration: rename ComponentProvider to PluginComponentProvider, CreatePlugin to CreateComponent in effort to use consistent vocabulary (#4806)
  • Declarative configuration: Update instrumentation config behavior to return empty object when not set (#4817)

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-specification/compare/v1.53.0...v1.54.0

]]> <![CDATA[Introduce vulnerability component]]> https://changelog.opentelemetry.io/entry/1992095227 1992095227 Mon, 09 Feb 2026 19:46:05 GMT Introduce a new security namespace Vulnerability.

Fields are taken from ECS Vulnerability namespace

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

]]> <![CDATA[2026.01]]> https://changelog.opentelemetry.io/entry/281917755 281917755 Sat, 31 Jan 2026 10:33:57 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.12...2026.01

]]> <![CDATA[v1.39.0]]> https://changelog.opentelemetry.io/entry/276169129 276169129 Mon, 12 Jan 2026 22:07:10 GMT 🛑 Breaking changes 🛑

  • rpc: Rename rpc.client|server.duration to rpc.client|server.call.duration, change RPC duration metrics from milliseconds to seconds, and clarify metric and span duration semantics for streaming. (#383, #2961)

  • rpc: Rename

  • rpc.grpc.request.metadata and rpc.connect_rpc.request.metadata to rpc.request.metadata

  • rpc.grpc.response.metadata and rpc.connect_rpc.response.metadata to rpc.response.metadata (#2869, #3169)

  • rpc: Merge rpc.method and rpc.service into fully-qualified rpc.method attribute. Clarify how to handle possible high cardinality of rpc.method in edge cases. Clarify rpc.method usage in span names. (#2863, #3196, #3223)

  • rpc: Deprecate rpc.grpc.status_code, rpc.connect_rpc.error_code and rpc.jsonrpc.error_code attributes in favor of the more general rpc.response.status_code attribute. (#1504, #2920)

  • rpc: Align RPC conventions with naming guidelines. Renames:

  • rpc.system to rpc.system.name. The values are also updated to match naming guidelines: connect_rpc is renamed to connectrpc; apache_dubbo is renamed to dubbo; java_rmi, dotnet_wcf, and onc_rpc are not included in the new enum.

  • rpc.jsonrpc.request_id to jsonrpc.request.id.

  • rpc.jsonrpc.version to jsonrpc.protocol.version. (#2703, #2921)

  • system, linux: Rename *.linux.memory metrics and attributes to *.memory.linux (#1661)

🚩 Deprecations 🚩

  • peer: The peer.service attribute has been deprecated in favor of service.peer.name. (#2945) The peer.service attribute has been renamed to service.peer.name to align with the service.{name|namespace} resource attributes.
  • process: Introduce process.unix.file_descriptor.count and process.windows.handle.count metrics. Deprecate process.open_file_descriptor.count (#3188)

💡 Enhancements 💡

  • cloud: Add gcp.agent_engine as a value for cloud.platform (#2957)

  • cloud: Add Oracle Cloud Infrastructure to SemConv Areas list (#3190)

  • cloud: Add Hetzner Cloud to cloud.provider and cloud.platform (#2758)

  • cloud: Add Linode (Akamai Cloud) to cloud.provider and linode_cloud_compute to cloud.platform (#2756)

  • cloud: Add Vultr Cloud to cloud.provider and cloud.platform (#2757)

  • k8s: Add missing entity associations to k8s and container metrics (#3213)

  • k8s: Adds k8s.pod.ip, k8s.pod.hostname and k8s.pod.start_time attributes (#3171)

  • k8s: Define missing roles for entity attributes (#3135)

  • k8s: Promote a selection of k8s and container attributes to alpha (#3120) The selected attributes being promoted are used by the Collector Contrib components that are targeting stability. See opentelemetry-collector-contrib/#44130

  • k8s: Define roles for k8s entities' attributes (#3017)

  • mcp: Add MCP semantic conventions (#2043, #2083)

  • otel: Add otel.event.name attribute for use by non-OTLP exporters and logging libraries. (#2913) The otel.event.name attribute can be used by:

    • Non-OTLP exporters to emit the EventName
    • Applications using existing logging libraries to add event name information that can be used to set the EventName field by Collector or SDK components

  • pprof: add various pprof attributes to support lossless conversion from and to OTel profiles. (#3078)

  • rpc: Use consistent set of attributes between RPC spans and metrics (#2922, #3197)

    • Use rpc.response.status_code on common metrics and spans.
    • Make error.type note consistent between metrics and spans.
    • Promote notes on rpc.method and rpc.service to attribute definition.

  • rpc: Mark rpc.system.name, rpc.method, rpc.service, server.address, and server.port as sampling relevant attributes in RPC spans. (#3202)

  • service: Splits service into three entities: namespace, service and instance. (#2880)

  • service: service.peer.name and service.peer.namespace have been introduced as the replacement for peer.service to describe remote services that use both a name and a namespace. (#2945) The peer.service attribute could not fully represent the service.{name|namespace} resource attributes; service.peer.name and service.peer.namespace provide a more complete representation.

🧰 Bug fixes 🧰

  • rpc: Demote server.address from required to conditionally required (when available) on RPC spans and metrics. Update server.port requirement level accordingly. (#3236)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.38.0...v1.39.0

]]> <![CDATA[v1.53.0]]> https://changelog.opentelemetry.io/entry/275292273 275292273 Fri, 09 Jan 2026 16:54:14 GMT What's Changed

Metrics

  • Stabilize part of Enabled SDK for synchronous instruments. (#4787)

Logs

  • Add optional Ergonomic API. (#4741)

SDK Configuration

  • Declarative configuration: clarify default behavior and validation requirements of create and parse. (#4780)
  • Declarative configuration: add optional programmatic customization to create, and add related supplemental guidelines. (#4777)
  • Declarative configuration: add links between SDK extension plugins and corresponding declarative config types. (#4802)
  • Declarative configuration: clarify Registry ComponentProvider type parameter (#4799)

Common

  • Stabilize complex AnyValue attribute value types and related attribute limits. (#4794)

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-specification/compare/v1.52.0...v1.53.0

]]> <![CDATA[Refine recording errors documentation to include logs and avoid span events]]> https://changelog.opentelemetry.io/entry/3117609973 3117609973 Wed, 07 Jan 2026 22:16:08 GMT Towards OTEP: Span Event API deprecation plan

Towards https://github.com/open-telemetry/opentelemetry-specification/issues/4429

Towards https://github.com/open-telemetry/opentelemetry-go-contrib/issues/7254#issuecomment-2975444593 Towards https://github.com/open-telemetry/opentelemetry-go-contrib/issues/7470

Supersedes https://github.com/open-telemetry/semantic-conventions/pull/2296

"Prototype" (do this across all instrumentation libraries in Go): https://github.com/open-telemetry/opentelemetry-go-contrib/issues/7254#issuecomment-3153698098

Note that this is needed toward stabilization of otelhttp which is the OTel Go instrumentation library for HTTP server and client as we want to have a clear and stable way on how to record errors.

Changes

  • Adds comprehensive guidance on recording errors via logs (event records) instead of span events
  • Clarifies the distinction between "error" and "failed operation" concepts
  • Deprecates the recommendation to use Span.RecordException for error recording
  • Establishes consistency requirements for error.type across all signals (spans, metrics, logs)

Other

I was also considering deprecating Semantic conventions for exceptions on spans, but decided to hold off and better scope it to a separate PR.

An next steps (probably after stabilizing parts of this document) we could deprecate:

Changing "error" into "exception" terminology (which better aligns with the specification e.g. Span.RecordException and current semantic conventions) can be done in a separate PR

I was thinking about adding error.stacktrace per 2025-12-09 Logs SIG meeting, but I felt that it would be better to scope it to a separate PR as this is already big enough. But probably we would prefer to use exception.* attributes anyway.

]]> <![CDATA[Stabilize complex AnyValue types and related attribute limits]]> https://changelog.opentelemetry.io/entry/3088916311 3088916311 Wed, 07 Jan 2026 16:05:16 GMT Fixes #4710

OTEP #4485 (Extending attributes to support complex values)

What

Stabilize the complex AnyValue attribute value types and the corresponding attribute limits. Simplifiy the Logs Data Model to rely on AnyValue and Attribute Collections instead of custom any / map<string, any> types.

Why

Per the OTEP-implementing PR #4485 tht was merged on 2025‑07‑15, so the 6‑month window ends around 2026‑01‑15. This PR is intended to be merged around 2026‑01‑15, in line with that requirement.

Stable exporters will be prohibited from emitting complex attributes by default on signals other than Logs until at least 6 months after this OTEP is merged.

OpenTelemetry Go and Java treat the common package as a stable cross‑cutting surface. They need these AnyValue types and limits to be Stable in the spec before they can add corresponding features to their APIs, SDKs, and exporters.

Prototypes

We have three independent prototypes that exercised the complex AnyValue attribute types and limits:

In summary, they:

  1. Validated that complex attributes can be represented and processed end‑to‑end using AnyValue.
  2. Confirmed that the specified attribute limits (length and count) are acceptable.
  3. Demonstrated that existing implementations can adopt complex attributes without breaking current stable behavior.

Other

I was thinking about adding something to spec-compliance-matrix.md, but I do not see any obvious place where it could be located. I think we can tackle it in a separate PR if there would be a demand for it.

EDIT: Tracked under https://github.com/open-telemetry/opentelemetry-specification/issues/4808

]]> <![CDATA[2025.12]]> https://changelog.opentelemetry.io/entry/274521736 274521736 Tue, 30 Dec 2025 11:32:19 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.11...2025.12

]]> <![CDATA[Release 1.52.0]]> https://changelog.opentelemetry.io/entry/269964030 269964030 Fri, 12 Dec 2025 17:13:53 GMT Context
  • Make the W3C randomness flag required. (#4761)

Traces

  • Deprecate Zipkin exporter document and make exporter implementation optional. (#4715)
  • Add spec for AlwaysRecord sampler (#4699)

Metrics

  • Stabilize Enabled API for synchronous instruments. (#4746)
  • Allow instrument Enabled implementation to have additional optimizations and features. (#4747)

Logs

  • Stabilize LogRecordProcessor.Enabled. (#4717)

SDK Configuration

  • Clarifies that guidance related to boolean environment variables is not applicable to other configuration interfaces. (#4723)

New Contributors

]]> <![CDATA[Define Nginx Ingress Controller events]]> https://changelog.opentelemetry.io/entry/1846364430 1846364430 Sun, 07 Dec 2025 03:42:55 GMT Changes

Following the events convention, adding definition for Nginx Ingress Controller events. All this information is from the Elastic Nginx Ingress Controller Logs integration.

Merge requirement checklist

]]> <![CDATA[2025.11]]> https://changelog.opentelemetry.io/entry/269068644 269068644 Sat, 29 Nov 2025 14:30:29 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.10...2025.11

]]> <![CDATA[Proposal for vector db semantic convention]]> https://changelog.opentelemetry.io/entry/1962658702 1962658702 Mon, 24 Nov 2025 21:30:09 GMT This is a proposal for vector db semantic convention (see #936). I tried to expand the db semantic convention adding some db.vector attributes. I tried to focus on the basic needs of a general purpose vector database.

I proposed the following experimental attributes (updated with the feedbacks in this PR):

db.search.similarity_metric: specify the metric used in similarity search (e.g. cosine)
db.record.id: the ID of the record (e.g. the ID of the vector)
db.vector.field_name: the name field of the vector embedding
db.vector.dimension_count: the dimension of the vector (e.g. 1536)
db.query.limit: the number of vectors returned by a query (e.g. top-k)

The operations performed in a vector db, such as insert, update, search and delete can be performed using the existing db.operation.name attribute.

Regarding the similarity search we can use the db.query attributes, such as db.query.parameter.<key>.

]]> <![CDATA[Release 1.51.0]]> https://changelog.opentelemetry.io/entry/262977801 262977801 Mon, 17 Nov 2025 14:01:39 GMT Metrics
  • AlignedHistogramBucketExemplarReservoir SHOULD use a time-weighted algorithm. (#4678)

Profiles

  • Document the profiles signal. (#4685)

Common

  • Extend the set of attribute value types to support more complex data structures. (#4651)

New Contributors

]]> <![CDATA[OTEP: Recording exceptions as log records]]> https://changelog.opentelemetry.io/entry/2225238408 2225238408 Tue, 11 Nov 2025 03:32:52 GMT Related to https://github.com/open-telemetry/semantic-conventions/issues/1536

Changes

Recording exceptions as span events is problematic since it

  • ties recording exceptions to tracing/sampling
  • duplicates exceptions recorded by instrumented libraries on logs
  • does not leverage log features such as typical log filtering based on severity

This OTEP provides guidance on how to record exceptions using OpenTelemetry logs focusing on minimizing duplication and providing context to reduce the noise.

If accepted, the follow-up spec changes are expected to replace existing (stable) documents:

]]> <![CDATA[2025.10]]> https://changelog.opentelemetry.io/entry/259158863 259158863 Fri, 31 Oct 2025 22:59:33 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.09...2025.10

]]> <![CDATA[v1.9.0]]> https://changelog.opentelemetry.io/entry/258902695 258902695 Fri, 31 Oct 2025 19:12:11 GMT Added
  • profiles: drop field profile.comment_strindices. #729
  • profiles: clarify the original payload field comments. #722
  • profiles: add a note about cardinality implications for attribute values. #713

Changed

  • profiles: clarify dictionary guidelines: duplicates and other restrictions. #732
  • profiles: clarify the original payload field comments. #722
  • profiles: rename line -> lines and sample -> samples since they are repeated fields. #712
  • profiles: document more explicitly the dictionary zero element requirement. #711
  • all: drop attribute values restrictions. #707
    ⚠️ IMPORTANT: OTLP consumers are expected to accept attribute values that were previously considered invalid. All attributes can now contain:
    • empty values,
    • bytes values,
    • array values different than array of string values, bool values, int values, double values,
    • kvlist values.

Fixed

  • all: fix schema_url comments to include scope field coverage. #727
  • all: add missing field comments. #717

Removed

  • profiles: drop field profile.comment_strindices. #729
  • profiles: remove aggregation temporality enum and field. #710

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-proto/compare/v1.8.0...v1.9.0

]]> <![CDATA[v1.38.0]]> https://changelog.opentelemetry.io/entry/258283246 258283246 Wed, 29 Oct 2025 20:17:50 GMT 🛑 Breaking changes 🛑

  • k8s: Rename k8s.node.allocatable.* metrics to k8s.node.*.allocatable (#2973) Renamed metrics:

    • k8s.node.allocatable.cpu -> k8s.node.cpu.allocatable
    • k8s.node.allocatable.memory -> k8s.node.memory.allocatable
    • k8s.node.allocatable.ephemeral_storage -> k8s.node.ephemeral_storage.allocatable

  • k8s: Fix plural-named updowncounter k8s metrics (#2301) Renamed metrics:

    • k8s.node.allocatable.pods -> k8s.node.pod.allocatable
    • k8s.daemonset.current_scheduled_nodes -> k8s.daemonset.node.current_scheduled
    • k8s.daemonset.desired_scheduled_nodes -> k8s.daemonset.node.desired_scheduled
    • k8s.daemonset.misscheduled_nodes -> k8s.daemonset.node.misscheduled
    • k8s.daemonset.ready_nodes -> k8s.daemonset.node.ready
    • k8s.job.active_pods -> k8s.job.pod.active
    • k8s.job.failed_pods -> k8s.job.pod.failed
    • k8s.job.successful_pods -> k8s.job.pod.successful
    • k8s.job.desired_successful_pods -> k8s.job.pod.desired_successful
    • k8s.job.max_parallel_pods -> k8s.job.pod.max_parallel
    • k8s.cronjob.active_jobs -> k8s.cronjob.job.active
    • k8s.deployment.desired_pods -> k8s.deployment.pod.desired
    • k8s.deployment.available_pods -> k8s.deployment.pod.available
    • k8s.replicaset.desired_pods -> k8s.replicaset.pod.desired
    • k8s.replicaset.available_pods -> k8s.replicaset.pod.available
    • k8s.replicationcontroller.desired_pods -> k8s.replicationcontroller.pod.desired
    • k8s.replicationcontroller.available_pods -> k8s.replicationcontroller.pod.available
    • k8s.statefulset.desired_pods -> k8s.statefulset.pod.desired
    • k8s.statefulset.ready_pods -> k8s.statefulset.pod.ready
    • k8s.statefulset.current_pods -> k8s.statefulset.pod.current
    • k8s.statefulset.updated_pods -> k8s.statefulset.pod.updated
    • k8s.hpa.desired_pods -> k8s.hpa.pod.desired
    • k8s.hpa.current_pods -> k8s.hpa.pod.current
    • k8s.hpa.max_pods -> k8s.hpa.pod.max
    • k8s.hpa.min_pods -> k8s.hpa.pod.min

  • process: Renames process.context_switch_type to process.context_switch.type (#1501)

  • rpc: Attributes for rpc metric are now explicitly associated with metrics. (#2311) The breaking change is due to the removal of network.type from the metrics.

  • system: Mark cpu.logical_number attribute as opt-in for system.cpu.time and system.cpu.utilization metrics (#2932)

  • system, process: Rename system.process.status to process.state (#1803)

  • system, process: Replace system.paging.type and process.paging.fault_type with system.paging.fault.type (#1803)

  • v8js: Rename metric v8js.heap.space.available_size to v8js.memory.heap.space.available_size. Rename metric v8js.heap.space.physical_size to v8js.memory.heap.space.physical_size. (#2856)

🚩 Deprecations 🚩

  • rpc: Deprecate rpc..requests_per_rpc and rpc..responses_per_rpc metrics. (#2784)
  • system: Fix deprecation of system.cpu.logical_number (#2700)

💡 Enhancements 💡

  • app: Add app.screen.name attribute to capture application screen names. (#2743)

  • cicd: Add guidance on per pipeline run metrics (#1184)

  • cicd: Improve the description of cicd.worker entities. (#1191)

  • cicd: Add guidance on CI/CD logs (#1714)

  • db: Add database context propagation via V$SESSION.ACTION for SQL Server (#2610)

  • gcp: Document gcp.apphub_destination.* attributes (#2649)

  • gen-ai: Add participant's name on generative AI chat message. (#2943)

  • gen-ai: Add tool definitions and execution details for Single and Multi-Agent systems

  • Add 'gen_ai.tool.definitions' attribute to 'invoke_agent' span

  • Add 'gen_ai.tool.definitions' attribute to 'attributes.gen_ai.inference.client' attribute group.

  • Add 'gen_ai.tool.call.arguments' and 'gen_ai.tool.call.result' attributes to 'execute_tool' span. (#2444, #591)

  • gen-ai: Introducing Evaluation Event in GenAI Semantic Conventions to represent and capture evaluation results. (#2563)

  • gen-ai: invoke_agent spans now include span kind (CLIENT/INTERNAL) guidance and clarify when server.* attributes should be set. (#2837)

  • gen-ai: Add reasoning content message parts for chat messages. (#1965)

  • gen_ai: Add gen_ai.embeddings.dimension.count attribute to capture the dimension count of embeddings. (#2361) The gen_ai.embeddings.dimension.count is added to the span.gen_ai.embeddings.client span and gen_ai.client.operation.duration metric.

  • gen_ai: Add multimodal uri, file, and blob parts to GenAI JSON Schemas (#1556)

  • gen_ai, db, enduser, messaging: Fix deprecation reasons - use uncategorized when attribute type is changing. Fix missing/invalid deprecations on (deprecated) gen_ai.system attribute. (#2688)

  • http: Adds in the HTTP QUERY method. (#2642)

  • http: Clarify value for http.route attribute may contain static and dynamic segments. (#2616)

  • k8s: Add container CPU limit/request utilization metrics. (#1489)

  • k8s: Add k8s.pod.status.phase and k8s.pod.status.reason metrics (#2075)

  • k8s: Add memory metrics for k8s.node, k8s.pod and container resources (#2776)

  • nfs: Add nfs.* metrics, along with supporting rpc.onc.*/rpc.nfs.* attributes. (#39978)

  • openshift: Adds metrics for openshift's clusterquota (#2078)

  • pprof: Introduce pprof attributes. (#2522)

  • pprof: add attribute pprof.profile.comment. (#2861)

  • process: Increases the amount of attributes which are used to describe the running process. (#2655)

  • rpc: JSON-RPC now has its own span definition. (#2228)

  • rpc: Adds in network.protocol.name and network.protocol.version to all RPC spans and metrics. (#2719)

  • rpc: Adds in explicit span definitions for Connect RPC. (#2720)

  • rpc: Remove network.type attribute from RPC spans and metrics (#2851) The network.type attribute is no longer included in RPC semantic conventions. It remains available in the attribute registry for opt-in usage when needed.

  • rpc: Adds in explicitly defined grpc spans. (#2720)

  • rpc: Update the RPC stability warning and guidance for instrumentation authors (#2718)

  • rpc: The rpc spans now contains the error.type attribute to report the type of error that occurred. (#2812)

🧰 Bug fixes 🧰

  • dns: Simplify dns.question.name note to remove incorrect custom encoding requirements (#2143) The note now simply states that the domain name should be captured as it appears in the DNS query without any additional normalization, removing the previous incorrect custom encoding requirements.

  • nfs: nfs/metrics.yaml: nfs.server.net.count: add missing network.transport attribute. Implementation not merged, so not a breaking change. (#39978)

  • system: The system.network.dropped and system.network.packets metrics have been added as deprecated rather than being removed. (#2828)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.37.0...v1.38.0

]]> <![CDATA[Recommend using a time-unbiased reservoir sampling algorithm for histograms]]> https://changelog.opentelemetry.io/entry/2890377910 2890377910 Tue, 28 Oct 2025 23:10:27 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4675

Changes

Change the recommended algorithm for histogram reservoirs to be time-unbiased.

I've left the previous algorithm as an option to ensure this change is backwards-compatible.

Go prototype: https://github.com/open-telemetry/opentelemetry-go/pull/7458

  • Links to the prototypes (when adding or changing features)
  • CHANGELOG.md file updated for non-trivial changes
]]> <![CDATA[Release 1.50.0]]> https://changelog.opentelemetry.io/entry/255342416 255342416 Fri, 17 Oct 2025 14:41:29 GMT Traces
  • Restore TraceIdRatioBased and give it a deprecation timeline. Update recommended warnings based on feedback in issue #4601. (#4627)
  • Changes of TracerConfig.disabled MUST be eventually visible. (#4645)
  • Remove text related to the former expermental probability sampling specification. (#4673)

Metrics

  • Changes of MeterConfig.disabled MUST be eventually visible. (#4645)

Logs

  • Add minimum_severity and trace_based logger configuration parameters. (#4612)
  • Changes of LoggerConfig.disabled MUST be eventually visible. (#4645)

New Contributors

]]> <![CDATA[OTEP: Define EntityProvider]]> https://changelog.opentelemetry.io/entry/2211291702 2211291702 Wed, 01 Oct 2025 03:30:47 GMT This OTEP defines a EntityProvider, to enable the updating of resources that have a lifespan shorter than the lifespan of the application instance.

This OTEP is currently a draft. The primary open question is how to handle active spans that are already running when a resource change is made. Please see the OTEP for details.

]]> <![CDATA[2025.09]]> https://changelog.opentelemetry.io/entry/251368401 251368401 Tue, 30 Sep 2025 20:45:54 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.08...2025.09

]]> <![CDATA[Release 1.49.0]]> https://changelog.opentelemetry.io/entry/247725646 247725646 Tue, 16 Sep 2025 17:37:07 GMT Entities
  • Specify entity information via an environment variable. (#4594)

Common

  • OTLP Exporters may allow devs to prepend a product identifier in User-Agent header. (#4560)
  • ⚠️ IMPORTANT: Extending the set of standard attribute value types is no longer a breaking change. (#4614)

OTEPs

  • Clarify in Composite Samplers OTEP the unreliable threshold case. (#4569)

New Contributors

]]> <![CDATA[v1.8.0]]> https://changelog.opentelemetry.io/entry/244161184 244161184 Tue, 02 Sep 2025 15:03:39 GMT Changed
  • profiles: drop gzip requirement. #661
  • profiles: avoid optional keyword usage. #659
  • profiles: make profile_id optional. #665
  • profiles: use single Profile.sample_type and clarify use of timestamps. #649
  • all: add notes about the attribute values restrictions. #683
    ⚠️ IMPORTANT: These restrictions can be dropped in a future minor release.
  • profiles: clarify usage of the zero value as the first element of tables in ProfilesDictionary. #688, #698
  • profiles: unsigned time_nanos and duration_nanos in Profile. #692
  • profiles: improve attribute encoding in ProfilesDictionary. #672
  • profiles: simplify profile stack trace representation. #708

Fixed

  • examples: fix OTLP JSON Event example body. #666
  • docs: minor specification fixes around UNAVAILABLE and RetryInfo. #669

Removed

  • profiles: remove default_sample_type. #679
  • profiles: remove has_* debug info fields, they are moving to attributes. #595
  • profiles: remove Location.is_folded. #690
]]> <![CDATA[2025.08]]> https://changelog.opentelemetry.io/entry/243922636 243922636 Sun, 31 Aug 2025 07:57:02 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.07...2025.08

]]> <![CDATA[v1.37.0]]> https://changelog.opentelemetry.io/entry/242411320 242411320 Mon, 25 Aug 2025 23:15:52 GMT 🛑 Breaking changes 🛑
  • gen-ai: Revamp how GenAI chat history is recorded. Instead of per-message events, we now have gen_ai.system_instructions, gen_ai.input.messages, and gen_ai.output.messages attributes that can appear on GenAI spans or the new gen_ai.client.inference.operation.details event. New attributes are not recorded by default when content capturing is disabled. Deprecations:
    • gen_ai.system.message event - use gen_ai.system_instructions or gen_ai.input.messages attributes instead.
    • gen_ai.user.message, gen_ai.assistant.message, gen_ai.tool.message events (use gen_ai.input.messages attribute instead)
    • gen_ai.choice event (use gen_ai.output.messages attribute instead) (#2010, #2179, #1913, #1621, #1912)
  • container: The container runtime can now also have the version and description provided (#2342)
  • gen-ai: Follow system-specific naming policy in GenAI semantic conventions.
    • Rename gen_ai.system to gen_ai.provider.name
    • Remove gen_ai prefix from gen_ai.openai.* attributes.
    • Rename az.ai.* attribute names to azure.ai.*. (#2046)
  • system: Rename system.network.dropped to system.network.packet.dropped and system.network.packets to system.network.packet.count (#1700)

💡 Enhancements 💡

  • all: Add metric_value_type code-generation annotation to all metric definitions. (#2444, #591)
  • http: Clarify how server.address and server.port should be populated by HTTP client instrumentations. (#2443, #2463)
  • otel: Add otel.scope.schema_url attribute to non-OTLP exporters that represents an instrumentation scope schema URL. (#2320, #2489)
  • aspnetcore: Add ASP.NET Core Identity metrics and update the registry. (#2509)
  • gen-ai: Add operation name and tool type attributes for Execute tool span. (#2525, #2526)
  • aspnetcore: Add ASP.NET Core authentication and authorization metrics and update the registry. (#2530)
  • aspnetcore: Add ASP.NET Core memory pool metrics and update the registry. (#2532)
  • app: Defines a new app.build_id attribute. (#2591)
  • k8s: Add k8s node, pod, container filesystem metrics (#1488)
  • k8s: Add k8s Pod Volume metrics (#1485)
  • messaging: Added in AWS SNS as messaging systems (#2266)
  • system: Used memory should be based on operating system's internals (#2534)
  • db: Add context propagation via SQL commenter for databases (#2162)
  • hardware: Move text hardware metrics to the hardware components, yaml and md files (#2380)
  • app: Defines a new jank event in the app domain (#2552)
  • docs: Document the "T-Shaped" notion for defining semantic conventions. (#2232)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.36.0...v1.37.0

]]> <![CDATA[[IMPORTANT] Extending attribute value types is no longer a breaking change]]> https://changelog.opentelemetry.io/entry/2722143608 2722143608 Tue, 19 Aug 2025 15:47:58 GMT Towards https://github.com/open-telemetry/opentelemetry-specification/issues/4602

Per OTEP: https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/4485-extending-attributes-to-support-complex-values.md#why-doesnt-this-require-a-major-version-bump

This basically reverts:

Before we did not have a consensus to extend the attribute value types. However, this has changed with:

Related proto PR:

As a follow-up I plan to create issues in all language repositories so that they can prepare their APIs and SDKs to extend the attribute value types.

]]> <![CDATA[OTEP: Pluggable Authentication Interface for OTLP Exporters in SDKs]]> https://changelog.opentelemetry.io/entry/2508609392 2508609392 Fri, 15 Aug 2025 03:36:15 GMT Hi all, Following discussions in recent OpenTelemetry SIG meetings regarding the need for supporting authentication plugins in SDK exporters, it was agreed that a formal proposal should be developed to standardize this capability across languages.

This requirement has been brought up in the past via multiple issues in defferent forms:

This PR introduces an OTEP that proposes a pluggable authenticator interface for OTLP exporters within OpenTelemetry SDKs. The goal is to enable users to authenticate telemetry export requests without requiring custom exporter implementations. I’m opening this PR to initiate a broader discussion within the community and to collaboratively shape the direction of this feature.

I’ll update the description with additional context or background links as the discussion evolves. Looking forward to your feedback and contributions.

]]> <![CDATA[Release 1.48.0]]> https://changelog.opentelemetry.io/entry/239087603 239087603 Wed, 13 Aug 2025 15:49:11 GMT Logs
  • Improve concurrency safety description of LogRecordProcessor.OnEmit. (#4578)
  • Clarify that SeverityNumber values are used when comparing severities. (#4552)

Entities

  • Mention entity references in the stability guarantees. (#4593)

OpenTelemetry Protocol

  • Clarify protocol defaults on specification. (#4585)

Compatibility

  • Flexibilie escaping of characters that are discouraged by Prometheus Conventions in Prometheus exporters. (#4533)
  • Flexibilize addition of unit/type related suffixes in Prometheus exporters. (#4533)
  • Define the configuration option "Translation Strategies" for Prometheus exporters. (#4533)
  • Define conversion of Prometheus native histograms to OpenTelemetry exponential histograms. (#4561)
  • Clarify what to do when scope attribute conflicts with name, version and schema URL. (#4599)

SDK Configuration

  • Enum values provided via environment variables SHOULD be interpreted in a case-insensitive manner. (#4576)

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-specification/compare/v1.47.0...v1.48.0

]]> <![CDATA[Add MeasurementProcessor to Metrics SDK]]> https://changelog.opentelemetry.io/entry/2212436058 2212436058 Wed, 06 Aug 2025 03:46:36 GMT Fixes #4298

This PR adds the MeasurementProcessor concept to the Metrics SDK specification.

The goal is to allow functionality such as:

  • Adding attributes, e.g., injection of additional attributes to measurements based on Context
  • Modifying attributes
  • Dropping attributes
  • Dropping individual measurements
  • Modifying measurements

Prototypes: Python: https://github.com/open-telemetry/opentelemetry-python/pull/4642 Rust: https://github.com/open-telemetry/opentelemetry-rust/pull/2797

]]> <![CDATA[2025.08]]> https://changelog.opentelemetry.io/entry/238256091 238256091 Thu, 31 Jul 2025 17:00:35 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.06...2025.08

]]> <![CDATA[2025.07]]> https://changelog.opentelemetry.io/entry/238256629 238256629 Thu, 31 Jul 2025 17:00:35 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.06...2025.07

]]> <![CDATA[Release 1.47.0]]> https://changelog.opentelemetry.io/entry/233559728 233559728 Fri, 18 Jul 2025 15:25:47 GMT Traces
  • Define sampling threshold field in OpenTelemetry TraceState; define the behavior of TraceIdRatioBased sampler in terms of W3C Trace Context Level 2 randomness. (#4166)
  • Define CompositeSampler implementation and built-in ComposableSampler interfaces. (#4466)
  • Define how SDK implements Tracer.Enabled. (#4537)

Logs

  • Stabilize Event Name parameter of Logger.Enabled. (#4534)
  • Stabilize SDK and No-Op Logger.Enabled. (#4536)
  • SeverityNumber=0 MAY be used to represent an unspecified value. (#4535)

Compatibility

  • Clarify expectations about Prometheus content negotiation for metric names. (#4543)

Supplementary Guidelines

  • Add Supplementary Guidelines for environment variables as context carrier specification. (#4548)

OTEPs

  • Extend attributes to support complex values. (#4485)

Common

  • Update spec to comply with OTEP-232. (#4529)

New Contributors

]]> <![CDATA[OTEP: Extending attributes to support complex values]]> https://changelog.opentelemetry.io/entry/2472611775 2472611775 Tue, 15 Jul 2025 17:14:04 GMT Related to #4468, #4414

This OTEP suggests a path forward on how to support complex attributes. It proposes to:

  • allow complex attributes on all signals by default on the API and SDK level
  • discourage them on metrics, resources, instrumentation scope, and identifying attributes on entities. If complex attribute is provided, it's probably by mistake, but we let backend decide.
  • provide guidance in semconv to default to flat attributes whenever possible and develop conventions with an assumption that complex attributes are not indexed, not queryable and not efficient.
  • documents how limits can apply to complex attributes (leaf nodes are counted towards the attribute count limit and are truncated based on the value limit) and suggests other ways to protect from users misusing complex attributes.

Having experimental phase for complex attributes limits the impact of this change and gives backends a graceful period to update.

]]> <![CDATA[v1.36.0]]> https://changelog.opentelemetry.io/entry/230206689 230206689 Sat, 05 Jul 2025 16:48:25 GMT 🚩 Deprecations 🚩
  • os: Adds the 'deprecated:' tag/attribute to the z_os enum value of os.type. This value was recently deprecated in v1.35.0. (#2479)

💡 Enhancements 💡

  • otel: Replaces otel.sdk.span.ended with otel.sdk.span.started and allow differentiation based on the parent span origin (#2431)
  • db: Add database context propagation via SET CONTEXT_INFO for SQL Server (#2162)
  • entities: Adds support for Entity registry and Entity stabilization policies. (#2246)

🧰 Bug fixes 🧰

  • cloud: Exclude deprecated Azure members from code generation on the cloud.platform attribute (#2477, #2455)

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.35.0...v1.36.0

]]> <![CDATA[Update spec to comply with OTEP-232]]> https://changelog.opentelemetry.io/entry/2545718592 2545718592 Tue, 01 Jul 2025 22:55:11 GMT Changes

This change brings the specification lifecycle phases in alignment with OTEP-232 which defines the maturity levels for OTel in general. Most of the changes should be non-contentious, but one aspect deserves discussion: should feature-freeze be mapped to Release Candidate?

Should the changelog be updated to include this change?

Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

]]> <![CDATA[v1.35.0]]> https://changelog.opentelemetry.io/entry/228907385 228907385 Mon, 30 Jun 2025 19:58:04 GMT 🛑 Breaking changes 🛑

  • azure: Align azure events, attributes, and enum members with general naming guidelines. (#608, #1708, #1698)

    • Renamed attributes:
      • az.service_request_id to azure.service.request.id
      • az.namespace to azure.resource_provider.namespace
    • Renamed events:
      • az.resource.log to azure.resource.log
    • Renamed enum members:
      • az.ai.inference to azure.ai.inference (on gen_ai.system)
      • az.ai.openai to azure.ai.openai (on gen_ai.system)
      • azure_aks to azure.aks (on cloud.platform)
      • azure_app_service to azure.app_service (on cloud.platform)
      • azure_container_apps to azure.container_apps (on cloud.platform)
      • azure_container_instances to azure.container_instances (on cloud.platform)
      • azure_functions to azure.functions (on cloud.platform)
      • azure_openshift to azure.open_shift (on cloud.platform)
      • azure_vm to azure.vm (on cloud.platform)

  • system: Revert the change that moved system.cpu.* to cpu.*. The 3 affected metrics are back in system.cpu.*. (#1873)

  • system: Changes system.network.connections to system.network.connection.count (#1800)

  • k8s: Change instrument type for .limit/.request container metrics from gauge to updowncounter (#2354)

🚩 Deprecations 🚩

  • os: Deprecate os.type='z_os' and replace with os.type='zos' (#1687)

🚀 New components 🚀

  • mainframe, zos: Add initial semantic conventions for mainframes (#1687)

💡 Enhancements 💡

  • dotnet: Define .NET-specific network spans for DNS resolution, TLS handshake, and socket connections, along with HTTP-level spans to (optionally) record relationships between HTTP requests and connections. (#1192)

  • k8s: Add k8s.node.allocatable.cpu, k8s.node.allocatable.ephemeral_storage, k8s.node.allocatable.memory, k8s.node.allocatable.pods metrics (#2243)

  • k8s: Add k8s.container.restart.count metric (#2191)

  • k8s: Add K8s container resource related metrics (#2074)

  • k8s: Add k8s.container.ready metric (#2074)

  • k8s: Add k8s.node.condition metric (#2077)

  • k8s: Add k8s resource quota metrics (#2076)

  • events: Update general event guidance to allow complex attributes on events and use them instead of the body fields. (#1651, #1669)

  • k8s: Add k8s.container.status.state and k8s.container.status.reason metrics (#1672)

  • feature_flags: Mark feature flag semantic convention as release candidate. (#2277)

  • k8s: Add new resource attributes for k8s.hpa to capture the scaleTargetRef fields (#2008) Adds below attributes to the k8s.hpa resource:

    • k8s.hpa.scaletargetref.kind
    • k8s.hpa.scaletargetref.name
    • k8s.hpa.scaletargetref.api_version

  • k8s: Adds metrics and attributes to track k8s HPA's metric target values for CPU resources. (#2182) Below metrics are introduced to provide insight into HPA scaling configuration for CPU.

    • k8s.hpa.metric.target.cpu.value
    • k8s.hpa.metric.target.cpu.average_value
    • k8s.hpa.metric.target.cpu.average_utilization

  • k8s: Explains the rationale behind the Kubernetes resource naming convention. (#2245)

  • all: Adds modelling guide for resource and entity. (#2246)

  • service: Adds stability policies for Entity groups. (#2378) Entity groups now require role to be filled for attributes.

  • otel: Specifies component.type values for Zipkin and Prometheus exporters (#2229)

🧰 Bug fixes 🧰

  • otel: Removes otel.scope entity. (#2310)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.34.0...v1.35.0

]]> <![CDATA[2025.06]]> https://changelog.opentelemetry.io/entry/229013097 229013097 Mon, 30 Jun 2025 16:15:27 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.05...2025.06

]]> <![CDATA[`SeverityNumber=0` MAY be used to represent an unspecified value]]> https://changelog.opentelemetry.io/entry/2563003558 2563003558 Tue, 24 Jun 2025 16:06:12 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4478

Changes

Per https://github.com/open-telemetry/opentelemetry-specification/pull/4509#issuecomment-2913093472

The same is probably done in many languages. Shouldn't we say somewhere in specification that 0 is a "reserved" value as it may be used to model unspecified?

Yes, I think we can.

The main purpose of this PR would then be to allow to have 0 as a "reserved" value as this is how most implementations implement the "unspecified" value e.g.

Defining 0 as something else would be disruptive for these languages. If it would be safe to "reserve" this value and make it optional.

I guess only OTel Rust and OTel Swift have "proper" enums which does not require handling 0 as unspecified.

]]> <![CDATA[sdk_exporters/prometheus: Clarify Content Negotiation]]> https://changelog.opentelemetry.io/entry/2568553766 2568553766 Tue, 24 Jun 2025 14:46:14 GMT Changes

Addressing feedback received during the last Spec SIG meeting, I'm splitting my previous PR(https://github.com/open-telemetry/opentelemetry-specification/pull/4533) into two to ensure we keep the scope of the original one for the configuration changes.

If I understand correctly, almost all SDKs (if not all) are already compliant since they are wrappers around Prometheus SDKs, and Prometheus SDKs already do content negotiation properly. Then the PoCs are already done :)

]]> <![CDATA[Unset log record severity is not INFO]]> https://changelog.opentelemetry.io/entry/2517290365 2517290365 Sat, 21 Jun 2025 03:31:35 GMT Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4478

What

Remove the possibility that backends or UI may represent log records with unset severity as INFO severity. Source formats that do not define a concept of severity or log level SHOULD emit INFO.

Why

This changes the a possibility (MAY) to a recommendation (SHOULD). Therefore, I think it is an acceptable change for a Stable document.

I feel that this change can be considered as a bugfix given the specification already says:

https://github.com/open-telemetry/opentelemetry-specification/blob/aff95e535d4c57a6778145d7474201c5890db559/specification/logs/data-model.md#L287-L289

The "unset" value is 0 which is e.g. less severe than TRACE=1. Interpreting "unset" 0 as INFO=9 is against the statement above.

As the Logs SIG, we may also think that there may be use cases where the unspecified log record severity may be important. For instance, events may need separate more domain-specific severity levels.

We can't ever fully get rid of the possibility of the severity level being unset. However, reducing the chance of having this case would be beneficial and make processing easier. One can always add a processor which changes the severity level from unset to INFO.

An alternative could be that the SDK always sets the the severity level to INFO for those that log record that have been emitted with unset severity level. However, this closes the door of explicitly taking advantage of an unset severity level. People can always add a processor that sets the severity level to INFO if it was not set.

]]> <![CDATA[Add specification text for OTEP-0250]]> https://changelog.opentelemetry.io/entry/2424045450 2424045450 Mon, 16 Jun 2025 23:28:39 GMT Part of #1413 Part of #173 Part of #1060 Part of #1844

Prototypes

Rust, Go, Java

https://github.com/jmacd/rust-sampler https://github.com/jmacd/go-sampler https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/consistent-sampling/src/main/java/io/opentelemetry/contrib/sampler/consistent56

Changes

Adds specification text for OTEP-0250, which covers CompositeSampler and related interfaces.

]]> <![CDATA[Stabilize SDK and No-Op Logger.Enabled]]> https://changelog.opentelemetry.io/entry/2563042369 2563042369 Mon, 16 Jun 2025 23:01:23 GMT This part of the specification can be stabilized. It primarily defines how the SDK should respond to Logger.Enabled calls. I believe adding new rules in this context should not be considered breaking changes.

Notice that Logger.Enabled API has been already stabilized in https://github.com/open-telemetry/opentelemetry-specification/pull/4463.

]]> <![CDATA[Stabilize Event Name parameter of Logger.Enabled]]> https://changelog.opentelemetry.io/entry/2562917321 2562917321 Mon, 16 Jun 2025 22:39:57 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4528

What are you trying to achieve?

Stabilize Event Name parameter of Logger.Enabled.

Implemented by:

Additional context.

Related issue:

Related PR:

]]> <![CDATA[Release 1.46.0]]> https://changelog.opentelemetry.io/entry/224931646 224931646 Thu, 12 Jun 2025 14:45:53 GMT Metrics
  • Prometheus receiver can expect otel_scope_schema_url and otel_scope_[attribute] labels on all metrics. (#4505)
  • Prometheus receiver no longer expects otel_scope_info metric. (#4505)
  • Prometheus exporter adds otel_scope_schema_url and otel_scope_[attribute] labels on all metrics. (#4505)
  • Prometheus exporter no longer exports otel_scope_info metric. (#4505)

Entities

  • Define rules for setting identifying attributes. (#4498)
  • Define rules for entity-resource referencing model. (#4499)

Common

  • Move Instrumentation Scope definition from glossary to a dedicated document and use normative language. (#4488)
]]> <![CDATA[Have InstrumentationScope use normative language]]> https://changelog.opentelemetry.io/entry/2481791020 2481791020 Fri, 06 Jun 2025 14:12:22 GMT Fixes #4450

Moved the InstrumentationScope definition from glossary into common/instrumentation-scope.md, and massaged it using normative language, including some examples. Also removed the compile-time concept restriction (as clarified in the related issue, this limitation does not exist in a few SIGs).

]]> <![CDATA[prometheus: handle schema URL and scope attributes]]> https://changelog.opentelemetry.io/entry/2516224378 2516224378 Thu, 05 Jun 2025 16:56:34 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4223

Prototypes:

Changes

Currently (before this PR) Prometheus and OpenMetrics Compatibility assumes that only scope name and scope version are identifying.

However, with https://github.com/open-telemetry/opentelemetry-specification/pull/4161 this is no longer true.

Therefore, this PR updates the Prometheus and OpenMetrics Compatibility specification to add the scope name, version, schema URL, scope attributes to all metrics.

This also removes the otel_scope_info as it looks that it won't be useful. See: https://github.com/open-telemetry/opentelemetry-specification/issues/4223#issuecomment-2875819391.

This change important for Collector https://github.com/open-telemetry/opentelemetry-go/issues/5846#issuecomment-2828234292. It is also is necessary towards stabilization of OTel-Prom/OpenMetrics compatibility) and the Prometheus exporter.

Initially, I thought about splitting it into a few PRs. However, it looks like doing it in one PR would be a more complete approach (also there are not that many changes).

]]> <![CDATA[Initial semantic conventions for mainframes]]> https://changelog.opentelemetry.io/entry/2276648526 2276648526 Wed, 04 Jun 2025 13:43:57 GMT Fixes #1687

Changes

This PR lays out the initial structure of the semantic conventions for mainframes.

The PR adds the following new components to the semantic conventions:

  1. mainframe: Adds single attribute to registry right now, (planned for platform-specific definitions moving forward)
  2. zos: Adds z/OS related attributes and definition of z/OS system software resource (zos.software)

The PR is based on the input from the Mainframe SIG meetings to define initial semantic conventions for the mainframe.

Note

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

]]> <![CDATA[[spec] add `EnvVarPropagator` decorator for env variable context]]> https://changelog.opentelemetry.io/entry/2470126278 2470126278 Tue, 03 Jun 2025 20:47:52 GMT propagation

Fixes #4470

Changes

Changelog has been updated to reflect that addition of the EnvVarPropagator decorator for the TextMapPropagator

]]> <![CDATA[2025.05]]> https://changelog.opentelemetry.io/entry/222434826 222434826 Mon, 02 Jun 2025 13:10:52 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.04...2025.05

]]> <![CDATA[[entities] Define rules for setting identifying attributes]]> https://changelog.opentelemetry.io/entry/2505692192 2505692192 Thu, 22 May 2025 22:24:58 GMT Add a requirement that each entity type must have a canonical set of identifying attributes. Observers unable to provide the full set must either defer to another source or use a different entity type.

Resolves https://github.com/open-telemetry/opentelemetry-specification/issues/4253

]]> <![CDATA[v1.7.0]]> https://changelog.opentelemetry.io/entry/220078116 220078116 Wed, 21 May 2025 13:36:51 GMT This release only changes Profile signal, and unblocks the new Dictionary-based approach to attributes for Profiling.

What's Changed

Full Changelog: https://github.com/open-telemetry/opentelemetry-proto/compare/v1.6.0...v1.7.0

]]> <![CDATA[v1.34.0]]> https://changelog.opentelemetry.io/entry/219610595 219610595 Mon, 19 May 2025 19:44:40 GMT v1.34.0

🛑 Breaking changes 🛑

  • all: Convert deprecated text to structured format. (#2047) This is a breaking change from the schema perspective, but does not change anything for instrumentations or the end users. It breaks compatibility with the (old) code generation tooling. Please use weaver to generate Semantic Conventions markdown or code.

  • feature_flag: Move the evaluated value from the event body to attributes (#1990)

  • process: Require sensitive data sanitization for process.command_args and process.command_line (#626)

💡 Enhancements 💡

  • docs: Document system-specific naming conventions (#608, #1494, #1708)
  • gen-ai: Add gen_ai.conversation.id attribute (#2024)
  • all: Renames all resource.* groups to be entity.* (#2244) Part of open-telemetry/opentelemetry-specification#4436
  • aws: Added new AWS attributes for various services including SQS, SNS, Bedrock, Step Functions, Secrets Manager and Kineses (#1794)
  • cloud: Broaden cloud.region definition to explicitly cover both resource location and targeted destination. (#2142)
  • network: Stabilize network.transport enum value quic. (#2275)

🧰 Bug fixes 🧰

  • db: Fix the db.system.name attribute value for MySQL which was incorrectly pointing to microsoft.sql_server. (#2276)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.33.0...v1.34.0

]]> <![CDATA[Release 1.45.0]]> https://changelog.opentelemetry.io/entry/218608799 218608799 Wed, 14 May 2025 15:48:40 GMT Context
  • Drop reference to binary Propagator. (#4490)

Logs

  • Add optional Event Name parameter to Logger.Enabled and LogRecordProcessor.Enabled. (#4489)

Resource

  • Add experimental resource detector name. (#4461)

OTEPs

  • OTEP: Span Event API deprecation plan. (#4430)
]]> <![CDATA[[Logs] Add optional Event Name parameter to Logger.Enabled and LogRecordProcessor.Enabled]]> https://changelog.opentelemetry.io/entry/2485216513 2485216513 Tue, 13 May 2025 15:05:16 GMT Fixes #4220

Already used by Rust; https://github.com/open-telemetry/opentelemetry-specification/issues/4220#issuecomment-2828399052:

Yes. Otel Rust already has more parameters for the Enabled() check.

We expect to use that in Etw/user_events exporters scenarios, where we ask the OSKernel about whether a given event is interesting or not. Its currently leveraging severity only, but we expect to leverage EventName(and scope too) in the future.

OTel Go prototype: https://github.com/open-telemetry/opentelemetry-go/pull/6702

]]> <![CDATA[Stabilize reuse of Standard Attributes in Logs API]]> https://changelog.opentelemetry.io/entry/2443383679 2443383679 Mon, 12 May 2025 03:31:12 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4460

From the issue comments:

This seems to be supported by following languages:

Related: #4462 (comment) - if we end up formally documenting that having extended attributes on the API level is acceptable, we might want to reword this section a bit

I think it should be still possible to reword it in a backwards compatible way (given it occurs to be needed). At least personally I do not see how the proposals you mentioned would make the section "reuse of Standard Attributes" not compatible.

]]> <![CDATA[v1.33.0]]> https://changelog.opentelemetry.io/entry/216241537 216241537 Fri, 02 May 2025 19:46:16 GMT This release marks the first where the core of database semantic conventions have stabilized.

🛑 Breaking changes 🛑

  • db: Add db.query.parameter, replace relevant usages of db.operation.parameter (#2093)
  • db: Make db.response.returned_rows opt-in on release_candidate spans (#2211)
  • db: Use | as the separator when db.namespace is a concatenation of multiple components. (#2067)
  • feature_flag: Rename feature_flag.provider_name to feature_flag.provider.name (#1982)
  • feature_flag: Use generic error.message in feature flag evaluation event (#1994)
  • gen-ai: Refine the values for gen_ai.system related to Google's AI endpoints. (#1950) Enable sharing of attributes between Vertex AI and Gemini through a common prefix.
  • k8s: Make k8s Node and Pod labels optional (#2079)
  • otel: Rename span health metrics to remove the .count suffixes (#1979)

🚀 New components 🚀

  • db: Adding semantic conventions for oracledb instrumentations. (#2612) Oracle Database semantic conventions.
  • browser: Add browser web vitals event. (#1940)

💡 Enhancements 💡

  • cicd: Add resource conventions for CICD systems and define spans for CICD pipeline runs. (#1713) Define spans cicd.pipeline.run.server and cicd.pipeline.task.internal. Add cicd.pipeline.action.name, cicd.worker.id, cicd.worker.name, cicd.worker.url.full andcicd.pipeline.task.run.result to attribute registry. Define resources cicd.pipeline, cicd.pipeline.run and cicd.worker. Add entity associations in cicd metrics for these new cicd resources.
  • vcs: Add resource conventions for VCS systems and VCS references. (#1713) Define resources vcs.repo and vcs.ref. Add entity associations in vcs metrics for these new vcs resources.
  • gen-ai: Adding span for invoke agent (#1842)
  • gen-ai: Adding gen_ai.tool.description to the span attributes (#2087)
  • gen-ai: Separate inference and embeddings span definitions, remove irrelevant attributes from the create agent span. (#1924, #2122)
  • general: Provide guidance on modeling lat/lon, x/y, etc (#2145)
  • db: Move db.query.parameter.<key> from release_candidate back to development. (#2194)
  • db: Mark database semantic conventions as stable for MariaDB, Microsoft SQL Server, MySQL, and PostgreSQL. (#2199)
  • db: Make db.operation.name required where it's available, add recommendation for instrumentation point. (#2200, #2098)
  • db: Add db.stored_procedure.name to the general span conventions (#2205)
  • db: Add an option to generate db.query.summary from operation name and target, remove it from CosmosDB. (#2206)
  • db: Add db.operation.name and db.collection.name to SQL for higher-level APIs (#2207)
  • jvm: Add jvm.file_descriptor.count as an in-development metric to track the number of open file descriptors as reported by the JVM. (#1838)
  • jvm: Add jvm.gc.cause to metric jvm.gc.duration as an opt-in attribute to track gc cause. (#2065)
  • process: Add process.environment_variable. (#672)
  • app: Defines two new click events for the app domain (#2070)
  • code: Mark code.* semantic conventions as stable (#1377)
  • k8s: Introduce semantic conventions for k8s CronJob labels and annotations (#2138)
  • k8s: Introduce semantic conventions for k8s DaemonSet labels and annotations (#2136)
  • k8s: Introduce semantic conventions for k8s Deployment labels and annotations (#2134)
  • system: Added entity association template rendering and policies. (#1276)
  • gen_ai: Document generate_content as a permissible value of gen_ai.operation.name. (#2048)
  • k8s: Introduce semantic conventions for k8s Job labels and annotations (#2137)
  • otel: Adds SDK self-monitoring metrics for metric processing (#2016)
  • k8s: Introduce semantic conventions for k8s Namespace labels and annotations (#2131)
  • k8s: Introduce semantic conventions for k8s Node labels and annotations (#2079)
  • k8s: Introduce semantic conventions for k8s ReplicaSet labels and annotations (#2132)
  • otel: Adds SDK self-monitoring metric for exporter call duration (#1906)
  • k8s: Introduce semantic conventions for k8s StatefulSet labels and annotations (#2135)

🧰 Bug fixes 🧰

  • gen-ai: Removed irrelevant response attributes on GenAI create agent span. (#1924, #2116)
  • vcs: Fix typo in gitea name (#2057)
  • gen-ai: Add invoke_agent as a member of gen_ai.operation.name (#2160)
  • db: Clarify db.query.summary for stored procedures (#2218)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.32.0...v1.33.0

]]> <![CDATA[Mark database semantic conventions as stable for MariaDB, Microsoft SQL Server, MySQL, and PostgreSQL]]> https://changelog.opentelemetry.io/entry/2490070345 2490070345 Fri, 02 May 2025 19:31:55 GMT Marking as ready to review, but need to hold off merging until last few PRs to land:

]]> <![CDATA[2025.04]]> https://changelog.opentelemetry.io/entry/216530557 216530557 Wed, 30 Apr 2025 21:49:36 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.03...2025.04

]]> <![CDATA[v1.6.0]]> https://changelog.opentelemetry.io/entry/215450915 215450915 Tue, 29 Apr 2025 11:38:10 GMT What's Changed

Added

  • resource: Add EntityRef. #635
  • general: add specs for empty telemetry envelopes. #622

Changed

  • logs: Stabilize event_name field in LogRecord message. #643
  • profiles: Move the lookup tables to ProfilesData. #644
  • profiles: Move default sample_type from the string table to sample_type. #620
  • general: remove comment on each service about keeping the RPC alive #637
  • metrics: clarify when bucket_counts array may be empty #619

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-proto/compare/v1.5.0...v1.6.0

]]> <![CDATA[OTEP: Span Event API deprecation plan]]> https://changelog.opentelemetry.io/entry/2354722177 2354722177 Fri, 25 Apr 2025 19:03:24 GMT Based on number of comments in related PRs and issues, please go to the "Files changed" tab and add your comment somewhere there (instead of leaving the comment directly on the conversation), so that we can have threaded discussions. Thank you ❤️.

Related to #4333, #4393, #4429, #4414

]]> <![CDATA[Add resource detector name]]> https://changelog.opentelemetry.io/entry/2420326659 2420326659 Wed, 23 Apr 2025 18:41:42 GMT All SDK extension plugin interfaces are referred to by name in declarative config.

For SDK extension plugin interfaces like exporters, processors, metric readers, we have well-defined sets of built-in implementations. E.g.:

  • span exporter: otlp, otlp_file, console, zipkin
  • metric exporter: otlp, otlp_file, console
  • log exporter: otlp, otlp_file, console
  • span processor: simple, batch
  • metric reader: periodic, prometheus
  • log processor: simple, batch

These well-defined names provide obvious choices to name things in the declarative config JSON schema.

Resource detectors are currently much more open ended, with no defined list of built-in detectors. This is a problem for declarative config because we want to have a config story where you can plug the same YAML into different SDK language implementation and get the same behavior. Without defining this list, users will have to carefully lookup language-specific resource detector names and modify their YAML accordingly. Yikes.

This PR solves this by:

  • Establishing that resource detectors have a name, used for reference in configuration (where declarative config is the primary use case but other config solutions could similarly use the name)
  • Provide normative language for naming resource detectors according the root namespace of attributes they (e.g. os resource detector populates os.* attributes)
  • Carve out a list of reserved resource detector names, which should become standard in SDK-implementations

See also https://github.com/open-telemetry/opentelemetry-configuration/pull/188 for a reference at how these resource detector names are used in declarative configuration.

cc @open-telemetry/configuration-approvers

]]> <![CDATA[mark code.* attributes as stable]]> https://changelog.opentelemetry.io/entry/2456246632 2456246632 Thu, 17 Apr 2025 00:31:02 GMT Fixes #1377

Changes

Promote release candidate attributes in code.* to stable.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • schema-next.yaml updated with changes to existing conventions. N/A: no change to the semantic conventions.
]]> <![CDATA[Release 1.44.0]]> https://changelog.opentelemetry.io/entry/212525895 212525895 Tue, 15 Apr 2025 14:51:58 GMT v1.44.0 (2025-04-15)

Context

  • Add context propagation through Environment Variables specification. (#4454)
  • On Propagators API, stabilize GetAll on the TextMap Extract. (#4472)

Traces

  • Define sampling threshold field in OpenTelemetry TraceState; define the behavior of TraceIdRatioBased sampler in terms of W3C Trace Context Level 2 randomness. (#4166)

Metrics

  • Clarify SDK behavior for Instrument Advisory Parameter. (#4389)

Logs

  • Add Enabled opt-in operation to the LogRecordProcessor. (#4439)
  • Stabilize Logger.Enabled. (#4463)
  • Stabilize EventName. (#4475)

Baggage

  • Add context (baggage) propagation through Environment Variables specification. (#4454)

Resource

  • Add Datamodel for Entities. (#4442)

SDK Configuration

  • Convert declarative config env var substitution syntax to ABNF. (#4448)
  • List declarative config supported SDK extension plugin interfaces. (#4452)

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry-specification/compare/v1.43.0...v1.44.0

]]> <![CDATA[Stabilize EventName]]> https://changelog.opentelemetry.io/entry/2443506865 2443506865 Fri, 11 Apr 2025 02:51:24 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4459

From the issue comments:

EventName looks to be already supported by:

See also: https://github.com/open-telemetry/opentelemetry-proto/pull/643

]]> <![CDATA[Stabilize `GetAll` in `TextMap` Extract]]> https://changelog.opentelemetry.io/entry/2434725836 2434725836 Thu, 10 Apr 2025 20:59:51 GMT Fixes #4471

Changes

Removes "In Development" status notice for GetAll

]]> <![CDATA[Create initial Entities data model specification.]]> https://changelog.opentelemetry.io/entry/2377019623 2377019623 Thu, 10 Apr 2025 16:42:10 GMT Adds an initial cut at the Entity DataModel specification from OTEP 256.

Changes

  • Adds information to Resource readme.
  • Creates an initial Resource DataModel with content from Entities SIG discussions on purpose and usage or Resource.
  • Creates an entities diretory for storing Entities DataModel.

See https://github.com/open-telemetry/opentelemetry-proto/pull/635 for related protocol change.

Prototypes:

]]> <![CDATA[2025.03]]> https://changelog.opentelemetry.io/entry/216530483 216530483 Mon, 31 Mar 2025 19:10:04 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.02...2025.03

]]> <![CDATA[v1.32.0]]> https://changelog.opentelemetry.io/entry/209388276 209388276 Mon, 31 Mar 2025 15:52:01 GMT 📣 This release is the second release candidate for the Database Semantic Conventions, with Database conventions stability planned to be declared in the subsequent release.

🛑 Breaking changes 🛑

  • device: Change the definition of device.id and make it opt-in. (#1874, #1951)
  • feature_flag: Rename evaluation to result for feature flag evaluation result attributes (#1989)

🚀 New components 🚀

  • app: Create app.installation.id attribute (#1874, #1897)
  • cpython: Add CPython runtime garbage collector metrics (#1930)

💡 Enhancements 💡

  • vcs: Add owner and provider name to VCS attribute registry (#1452)
  • vcs: Remove fallback value for VCS provider name attribute (#2020)
  • db: Truncate db.query.summary to 255 characters if parsed from the query (#1978)
  • db: Normalize spaces in db.operation.name (if any) (#2028)
  • db: db.operation.parameter.<key> should not be captured for batch operations (#2026)
  • db: Add db.stored_procedure.name (#1491)
  • gcp: Adds GCP AppHub labels for resource. (#2006)
  • error: Add error.message property for human-readable error message on events. (#1992)
  • profile: Extend the list of known frame types with a value for Go and Rust (#2003)
  • otel: Adds SDK self-monitoring metrics for log processing (#1921)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.31.0...v1.32.0

]]> <![CDATA[Add opt-in LogRecordProcessor.Enabled]]> https://changelog.opentelemetry.io/entry/2370145903 2370145903 Tue, 25 Mar 2025 21:55:00 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4363

Towards https://github.com/open-telemetry/opentelemetry-specification/issues/4208 (uses Severity Level passed via Logger.Enabled)

Towards stabilization of OpenTelemetry Go Logs API and SDK.

Use cases

Below are some use cases where the new functionality can be used:

  1. Bridge features like LogLevelEnabled in log bridge/appender implementations. This is needed for all (but one) currently supported log bridges in OTel Go Contrib.
  2. Configure a minimum log severity level for a certain log processor.
  3. Filter out log and event records when they are inside a span that has been sampled out (span is valid and has sampled flag of false).
  4. Efficiently support high-performance logging destination like Linux user_events and ETW (Event Tracing for Windows).
  5. Bridge Logs API to a language-specific logging library (the other way than usual).

Changes

Add Enabled opt-in operation to the LogRecordProcessor.

I created an OTEP first which was a great for having a lot of discussions and evaluations of different proposals:

Most importantly from https://github.com/open-telemetry/opentelemetry-specification/pull/4290#issuecomment-2662708938:

Among Go SIG we were evaluating a few times an alternative to provide some new "filter" abstraction which is decoupled from the "processor". However, we faced more issues than benefits going this route (some if this is described here, but there were more issues: https://github.com/open-telemetry/opentelemetry-go/pull/5825#issuecomment-2550967383 . With the current opt-in Processor.Enabled we faced less issues so far. We also do not want to replicate all features from the logging libraries. If someone prefer the log4j (or other) filter design then someone can always use a bridge and use log4j for filtering. Enabled callback hook is the simplest design (yet very flexible) which makes it easy to implement in the SDKs. This design is inspired from the design of the two most popular Go structured logging libraries: https://pkg.go.dev/log/slog (standard library) and https://pkg.go.dev/go.uber.org/zap.

It is worth to adding that Rust design is similar and it also has an Enabled hook. See https://github.com/open-telemetry/opentelemetry-specification/issues/4363#issuecomment-2660164716. Basically we want to add something like https://docs.rs/log/latest/log/trait.Log.html#tymethod.enabled to the LogRecordProcessor and allow users to implement Enabled in the way that it will meet their requirements.

I also want to call out form https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/0265-event-vision.md#open-questions:

How to support routing logs from the Logs API to a language-specific logging library

To support this we would need a log record processor which bridges the Logs API calls to given logging library. For such case we would need an Enabled hook in Processor to efficiently bridge Logger.Enabled calls. A filterer design would not satisfy such use case.

I decided to name the new operation Enabled as:

  1. this name is already used in logging libraries in many languages: https://github.com/open-telemetry/opentelemetry-specification/pull/4439#issuecomment-2718666805
  2. it matches the name of the API call (for all trace, metrics and logs APIs).

I was also considering OnEnabled to have the same pattern as for Emit and OnEmit. However, we already have ForceFlush and Shutdown which does not follow this pattern so I preferred to keep the simple Enabled name. For OnEmit I could also imagine OnEmitted (or OnEmitting) which does something after (or just before like we have OnEnding in SpanProcessor) OnEmit on all registered processors were called. Yet, I do not imagine something similar for Enabled as calling Enabled should not have any side-effects. Therefore, I decided to name it Enabled.

I want to highlight that a processor cannot assume Enabled was called before OnEmit, because of the following reasons:

  1. Backward compatibility – Existing processors may already perform filtering without relying on Enabled. For example: Add Advanced Processing to Logs Supplementary Guidelines #4407.
  2. Self-sufficiency of OnEmit – Since Enabled is optional, OnEmit should be able to handle filtering independently. A processor filtering events should do so in OnEmit, not just in Enabled.
  3. Greater flexibility – Some processors, such as the ETW processor, don’t benefit from redundant filtering. ETW already filters out events internally, making an additional check unnecessary.
  4. Performance considerations – Calling Enabled from OnEmit introduces overhead, as it requires converting OnEmit parameters to match Enabled's expected input.
  5. Avoiding fragile assumptions – Enforcing constraints that the compiler cannot validate increases the risk of introducing bugs.

This feature is already implemented in OpenTelemetry Go:

This feautre (however with some differences) is also avaiable in OTel Rust; https://github.com/open-telemetry/opentelemetry-specification/issues/4363#issuecomment-2660164716:

OTel Rust also has this capability. Here's an example where it is leveraged to improve performance by dropping unwanted log early. https://github.com/open-telemetry/opentelemetry-rust/blob/88cae2cf7d0ff54a042d281a0df20f096d18bf82/opentelemetry-appender-tracing/benches/logs.rs#L78-L85

]]> <![CDATA[Release 1.43.0]]> https://changelog.opentelemetry.io/entry/206535885 206535885 Tue, 18 Mar 2025 12:18:00 GMT v1.43.0 (2025-03-18)

Traces

  • Clarify STDOUT exporter format is unspecified. (#4418)

Metrics

  • Clarify the metrics design goal, scope out StatsD client support. (#4445)
  • Clarify STDOUT exporter format is unspecified. (#4418)

Logs

  • Clarify that it is allowed to directly use Logs API. (#4438)
  • Clarify STDOUT exporter format is unspecified. (#4418)

Supplementary Guidelines

  • Add Advanced Processing to Logs Supplementary Guidelines. (#4407)

OTEPs

  • Composite Head Samplers. (#4321)
]]> <![CDATA[Composite Head Samplers]]> https://changelog.opentelemetry.io/entry/2216309068 2216309068 Wed, 12 Mar 2025 15:03:23 GMT Changes

Migrating from https://github.com/open-telemetry/oteps/pull/250.

This is another approach for introducing Composite (Head) Samplers. The previous one (https://github.com/open-telemetry/oteps/pull/240) proved too large, with some controversial elements. This OTEP is a split-off from that one, focusing just on one area - new Composite Samplers.

Two prototypes exist for this functionality. We are seeking a third prototype.

In the Java-contrib repo: https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/consistent-sampling/README.md

In @jmacd's https://github.com/jmacd/go-sampler/blob/main/README.md.

]]> <![CDATA[v1.31.0]]> https://changelog.opentelemetry.io/entry/204874457 204874457 Tue, 11 Mar 2025 00:49:47 GMT 🛑 Breaking changes 🛑

  • code: code.function.name value should contain the fully qualified function name, code.namespace is now deprecated (#1677)

  • gen-ai: Introduce gen_ai.output.typeand deprecate gen_ai.openai.request.response_format (#1757)

  • mobile: Rework device.app.lifecycle mobile event. (#1880) The device.app.lifecycle event has been reworked to use attributes instead of event body fields. The ios.app.state and android.app.state attributes have been reintroduced to the attribute registry.

  • system: Move CPU-related system.cpu.* metrics to CPU namespace (#1873)

  • k8s: Change k8s.replication_controller metrics to k8s.replicationcontroller (#1848)

  • db: Rename db.system to db.system.name in database metrics, and update the values to be consistent with database spans. (#1581)

  • session: Move session.id and session.previous_id from body fields to event attributes, and yamlize session.start and session.end events. (#1845) As part of the ongoing migration of event fields from LogRecord body to extended/complex attributes, the session.start and session.end events have been redefined.

💡 Enhancements 💡

  • code: Mark code.* semantic conventions as release candidate (#1377)

  • gen-ai: Added AI Agent Semantic Convention (#1732, #1739)

  • db: Add database-specific notes on db.operation.name and db.collection.name for Cassandra, Cosmos DB, HBase, MongoDB, and Redis, covering their batch/bulk terms and lack of cross-table queries. (#1863, #1573)

  • gen-ai: Adds gen_ai.request.choice.count span attribute (#1888) Enables recording target number of completions to generate

  • enduser: Undeprecate 'enduser.id' and introduce new attribute enduser.pseudo.id (#1104) The new attribute enduser.pseudo.id is intended to provide a unique identifier of a pseudonymous enduser.

  • k8s: Add k8s.hpa, k8s.resourcequota and k8s.replicationcontroller attributes and resources (#1656)

  • k8s: How to populate resource attributes based on attributes, labels and transformation (#236)

  • process: Adjust the semantic expectations for process.executable.name (#1736)

  • otel: Adds SDK self-monitoring metrics for span processing (#1631)

  • cicd: Adds a new attribute cicd.pipeline.run.url.full and corrects the attribute description of cicd.pipeline.task.run.url.full (#1796)

  • user-agent: Add user_agent.os.name and user_agent.os.version attributes (#1433)

🧰 Bug fixes 🧰

  • process: Fix units of process.open_file_descriptor.count and process.context_switches (#1662)

New Contributors

Special thanks to @chalin with all the link-checking fixes ❤️

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.30.0...v1.31.0

]]> <![CDATA[Clarify that it is allowed to directly use Logs API]]> https://changelog.opentelemetry.io/entry/2367895427 2367895427 Mon, 10 Mar 2025 19:21:01 GMT Why

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4435

Left-over after:

What

Removed the sentence:

Application developers are NOT encouraged to call this API directly.

Added a sentence:

Yet, the Logs API can also be used directly if one prefers to couple the code to it instead of using a bridged logging library.

CC @yasmin-aumeeruddy

]]> <![CDATA[mark code.* attributes as release candidate]]> https://changelog.opentelemetry.io/entry/2190408245 2190408245 Thu, 06 Mar 2025 00:41:29 GMT Relates to #1377

Changes

This PR marks the non-deprecated code.* attributes as release candidate.

Merge requirement checklist

]]> <![CDATA[2025.02]]> https://changelog.opentelemetry.io/entry/206590672 206590672 Fri, 28 Feb 2025 20:05:01 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2025.01...2025.02

]]> <![CDATA[Kubernetes: How to populate resource attributes based on attributes, labels and transformation]]> https://changelog.opentelemetry.io/entry/2284266349 2284266349 Thu, 27 Feb 2025 16:23:57 GMT Fixes https://github.com/open-telemetry/semantic-conventions/issues/236

This is a new take on the issue. https://github.com/open-telemetry/semantic-conventions/pull/349 has been created before and not completed.

So what's the difference now?

  1. The proposed rules are already implemented in the OTel operator and work well: https://github.com/open-telemetry/opentelemetry-operator#configure-resource-attributes - the PR (at least in it's initial form) makes the operator implementation fully compatible with this spec PR.
  2. The specification work on service.instance.id has been completed - which was effectively a blocker before.

Merge requirement checklist

]]> <![CDATA[Release 1.42.0]]> https://changelog.opentelemetry.io/entry/201015209 201015209 Tue, 18 Feb 2025 20:16:41 GMT v1.42.0 (2025-02-18)

Traces

  • Deprecate exception.escaped attribute, add link to in-development semantic-conventions on how to record errors across signals. (#4368)
  • Define randomness value requirements for W3C Trace Context Level 2. (#4162)

Logs

  • Define how SDK implements Logger.Enabled. (#4381)
  • Logs API should have functionality for reusing Standard Attributes. (#4373)

SDK Configuration

  • Define syntax for escaping declarative configuration environment variable references. (#4375)
  • Resolve various declarative config TODOs. (#4394)
]]> <![CDATA[[db] rename `db.system` to `db.system.name` for metrics and update values]]> https://changelog.opentelemetry.io/entry/2341701869 2341701869 Tue, 18 Feb 2025 16:48:51 GMT Part of #1581 , relevant to #1734

Changes

Rename db.system to db.system.name for metrics, and update the values to be consistent with database spans.

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

]]> <![CDATA[Randomness requirements following W3C Trace Context level 2]]> https://changelog.opentelemetry.io/entry/1987742596 1987742596 Thu, 13 Feb 2025 16:38:20 GMT Changes

Updates Trace SDK and Propagator specifications with

  • List W3C propagator requirements (e.g., should propagate tracestate)
  • Introduce W3C Trace Context Level 2 w/ the Random flag
  • Define explicit randomness feature from OTEP 235, OTEP 261
  • Trace SDK default ID generator should include 56 bits of randomness in the correct location
  • Trace SDK for root spans: either set the random flag to confirm the above, or use an explicit randomness value.

Part of #1413. Part of #3602.

Product of the Sampling SIG members @kentquirk @kalyanaj @oertl @PeterF778 @yuanyuanzhao3 and myself.

]]> <![CDATA[Deprecate `exception.escaped` attribute, update exception example]]> https://changelog.opentelemetry.io/entry/2280793858 2280793858 Tue, 04 Feb 2025 17:29:08 GMT This is follow up on https://github.com/open-telemetry/semantic-conventions/pull/1716 - cross signal guidance on how to record errors (and exceptions) in instrumentations.

Changes

Follow up for https://github.com/open-telemetry/semantic-conventions/pull/1716

exception.escaped attribute is not used in practice within OTel instrumentations (checked Java, .NET, JS. Python, Go, C++ and Rust including contrib repos). OTel instrumentations, in general, don't record handled exceptions, i.e. virtually all exceptions we're recording in non-native instrumentations are expected to escape span scope.

The litmus test whether to record exception on spans is whether the instrumentation is going to set span status to ERROR due to this exception.

A way to record all sorts of exceptions is being introduced in https://github.com/open-telemetry/opentelemetry-specification/pull/4333 and leverages logs along with severity that conveys how critical the exception is in more expressive way than exception.escaped flag.

]]> <![CDATA[2025.01]]> https://changelog.opentelemetry.io/entry/206590553 206590553 Fri, 31 Jan 2025 22:55:03 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2024.12...2025.01

]]> <![CDATA[Define syntax for escaping declarative config env var substitution]]> https://changelog.opentelemetry.io/entry/2285204347 2285204347 Fri, 31 Jan 2025 15:23:58 GMT Resolves #3914.

An environment variable substitution reference which starts with $$ (i.e. $${API_KEY}) is escaped. Implementations should strip the leading $ character and not perform substitution (i.e. $${API_KEY} => ${API_KEY}).

See java implementation here: https://github.com/open-telemetry/opentelemetry-java/pull/7033

]]> <![CDATA[Logs API to have functionality for reusing Standard Attributes]]> https://changelog.opentelemetry.io/entry/2284584931 2284584931 Tue, 28 Jan 2025 17:41:19 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4201

Reference implementations:

Related Slack thread: https://cloud-native.slack.com/archives/C062HUREGUV/p1736545245331779

]]> <![CDATA[v1.30.0]]> https://changelog.opentelemetry.io/entry/196700798 196700798 Fri, 24 Jan 2025 19:04:57 GMT 🛑 Breaking changes 🛑

  • event: Deprecate event.name attribute in favor of the top level event name property on the log record (#1646)

  • gen_ai: Rename gen_ai.openai.request.seed to gen_ai.request.seed and use it on general GenAI conventions. (#1715)

  • db: Rename db.system to db.system.name and clean up its values. Rename db.elasticsearch.*, db.cassandra.*, db.cosmosdb.* attributes to elasticsearch.*, cassandra.*, and azure.cosmosdb.* respectively. Rename db.client.cosmosdb.* metrics to azure.cosmosdb.client.*. (#1581, #608)

  • code: rename code.function, code.lineno, code.column and code.filepath (#1377, #1599) code.function renamed to code.function.name code.lineno renamed to code.line.number code.column renamed to code.column.number code.filepath renamed to code.file.path

  • system: Replace system.network.state with network.connection.state (#308)

  • messaging: RabbitMQ: Specify how to populate messaging.destination.name (#1529)

🚀 New components 🚀

  • security-rule: Introducing a new security rule namespace (#903)

💡 Enhancements 💡

  • cloud: Add Oracle Cloud Infrastructure to Semantic Conventions (#1658)

  • gen_ai: Yamlify gen_ai events and clean up examples. (#1469)

  • cicd: Add CICD metrics (#1600) Makes the following changes:

    • Add metrics cicd.pipeline.run.duration, cicd.pipeline.run.active, cicd.worker.count, cicd.pipeline.run.errors and cicd.system.errors.
    • The CICD attributes cicd.pipeline.run.state, cicd.pipeline.result, cicd.system.component, cicd.worker.state have been added to the registry.

  • gen-ai: Adds OpenAI API compatible gen_ai.system attribute values: az.ai.openai, deepseek, gemini, groq, perplexity and xai. Elaborates that openai can be ambiguous due to API emulation. (#1655)

  • docs: Update attribute, events, and metrics naming guidance to include new best practices. (#1694)

    • Use namespaces (with . delimiter) whenever possible.
    • Use precise, descriptive, unambiguous names that leave room for expansion.

  • docs, db: Add common guidance for recording errors on spans and metrics, clarify DB conventions. (#1516, #1536, #1716)

  • gen-ai: Adds mistral_ai as a gen_ai.system attribute value. (#1719)

  • process: Update process.runtime example for the Python language. (#1772)

  • db: Add metrics section to each of the database system-specific conventions. (#1447, #1779)

  • k8s: Add metrics for k8s deployment, replicaset, replication_controller, statefulset and hpa. (#1636, #1637, #1644) This addition focused on providing consistency between these metrics, while also ensuring alignment with recommendations from Kubernetes. More details in #1637

  • k8s: Add k8s deamonset related metrics (#1649)

  • k8s: Add k8s metrics for job and cronjob (#1660)

  • k8s: Add k8s.namespace.phase metric along with the respective attribute (#1668)

  • aws: Add extended request ID to general AWS attributes as aws.extended_request_id (#1670)

  • messaging: Further clarify {destination} value on span names (#1635)

  • gen_ai: Introduce gen_ai.request.seed and deprecated gen_ai.openai.request.seed (#1710)

  • system: Adds note about how system.cpu.physical.count and system.cpu.logical.count are calculated (#1780)

  • k8s: Add migration guide for K8s semantic conventions (#1597)

  • profile: Extend the list of known frame types with a value for Erlang (#1735)

  • dotnet: Mark .NET runtime metrics as stable (#1602)

  • vcs: Adds vcs.repository.name attribute to registry and update vcs.repository.url.full description for consistent representation. Updates the VCS metrics to include vcs.repository.name as a recommended attribute. (#1254, #1453)

  • vcs: Add vcs.change.time_to_merge metric. (#1685)

New Contributors

Full Changelog: https://github.com/open-telemetry/semantic-conventions/compare/v1.29.0...v1.30.0

]]> <![CDATA[Release 1.41.0]]> https://changelog.opentelemetry.io/entry/195975020 195975020 Wed, 22 Jan 2025 02:59:59 GMT v1.41.0 (2025-01-21)

Logs

  • Remove the deprecated Events API and SDK in favor of having Events support in the Logs API and SDK. (#4353)
  • Remove Logger's Log Instrumentation operations. (#4352)
  • Make all Logger operations user-facing. (#4352)

SDK Configuration

  • Clarify that implementations should interpret timeout environment variable values of zero as no limit (infinity). (#4331)
]]> <![CDATA[logs: Remove Events operations in favor of making whole Logger user-facing]]> https://changelog.opentelemetry.io/entry/2266241518 2266241518 Wed, 15 Jan 2025 21:33:03 GMT Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4234 Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4275 Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4199 Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4357

This PR fixes more issues while making the design simpler than:

It does not break anything which was agreed on in https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/0265-event-vision.md.

I think we have gathered enough use cases to make emitting log records user-facing:

Other related OTEP PR:

Here is an OTel Go prototype pre-approved by @open-telemetry/go-maintainers :

I want to add that the other prototype following the current specification was not found acceptable for OTel Go SIG:

]]> <![CDATA[Clarify boundaries of numeric env vars]]> https://changelog.opentelemetry.io/entry/2225029816 2225029816 Wed, 15 Jan 2025 17:20:30 GMT Resolves #4283.

  • Adds new guidance indicates that for timeout variables, "implementations SHOULD interpret timeout values of zero as indefinite".
  • Clarifies range of acceptable values for OTEL_ATTRIBUTE_* / OTEL_SPAN_ATTRIBUTE_* / OTEL_LOGRECORD_ATTRIBUTE_*, OTEL_BSP_MAX_QUEUE_SIZE, OTEL_BLRP_MAX_QUEUE_SIZE.

Related PR to opentelemetry-configuration: https://github.com/open-telemetry/opentelemetry-configuration/pull/151

]]> <![CDATA[[configuration] Add exception for 'false default' when there is a double negation]]> https://changelog.opentelemetry.io/entry/2266180865 2266180865 Tue, 14 Jan 2025 21:36:07 GMT Relates to #4344.

Changes

Adds exception to naming and default value rule for environment variables.

This is a backwards compatible change since the original statement is phrased as a 'SHOULD'. The OTEL_SDK_DISABLED deviates from this new norm (this is not a spec violation but a lack of consistency).

The wording tries to be similar to the one in footnote [1] here: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.40.0/specification/protocol/exporter.md

There are several OpenTelemetry artifacts that are either not bound by the specification or have decided, for usability reasons, to not follow this rule in this case. This change would, I argue, bring more consistency and less confusion to end users.

I plan to submit a follow-up PR to change MeterConfig.disabled to MeterConfig.enabled if this PR is accepted. I don't plan to submit a PR to migrate OTEL_SDK_DISABLED, but this could be done if there is interest.

Thanks to @pellared for guidance on this :)

For non-trivial changes, follow the change proposal process.

]]> <![CDATA[Support complex attributes in the Event API]]> https://changelog.opentelemetry.io/entry/2227669614 2227669614 Tue, 14 Jan 2025 21:35:08 GMT Fixes #4199

Allow complex attributes on Events.

Based on discussion in https://github.com/open-telemetry/semantic-conventions/issues/1651 and in today's Specification SIG meeting (recording).

The biggest struggle currently for launching the Event API is the "two property bags" problem, also known as "do I put my event key/value pairs into event attributes or into the event body?"

The Log SIG has been trying to figure out a satisfactory answer to this for a month.

The proposal from @lmolkova is to put everything into event attributes, eliminating one of these "property bags" and answering the question of where to put event key/value pairs.

The event body could still potentially be used for dumping unstructured (or possibly very large) data.

To make this work, we need complex attributes on Events.

This would allow for example "locally scoped" attributes on an event to be defined as a complex attribute in the semantic conventions, e.g. an event named browser.page_navigation_timing could define a complex attribute in the semantic conventions named browser.page_navigation_timing (could be the same as the event name or different), which would contain it's "locally scoped" event attributes underneath it, e.g.

{
  "user.name": ...,
  ...,
  "browser.page_navigation_timing": {
    "name": ...,
    "fetchStart": ...,
    "unloadEventStart": ...,
    "unloadEventEnd": ...,
    ...
  },
  ...
}
]]> <![CDATA[add document defining an OpenTelemetry Collector]]> https://changelog.opentelemetry.io/entry/2204196325 2204196325 Tue, 14 Jan 2025 21:32:55 GMT Changes

Adds a definition of an OpenTelemetry Collector

]]> <![CDATA[OTEP: Logger.Enabled]]> https://changelog.opentelemetry.io/entry/2174465953 2174465953 Tue, 14 Jan 2025 21:32:36 GMT The main purpose of this OTEP is to have an agreement that the SDK needs both:

  • a "hook" for Logger.Enabled for customization and flexibility via extending LogRecordProcessor with Enabled method
  • new LoggerConfig fields to conveniently address the most popular, especially configuring the minimum severity level

The OTEP tries to elaborate how/why it should work well with (trace) sampling as well as Events API.

  • New issues are going to be created if this OTEP is accepted and merged.
  • Each "alternative" and "open question" would also have a new issue for tracking purposes (to explicitly reject or accept them).
  • I will follow-up on the most important issues which looks to be
    • Add Enabled method to LogRecordProcessor (and describe how SDK evaluates the Logger.Enabled API)
    • Add minimum_severity_level field to LoggerConfig (and describe how SDK evaluates the Logger.Enabled API)

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4207

]]> <![CDATA[2024.12]]> https://changelog.opentelemetry.io/entry/206590463 206590463 Tue, 31 Dec 2024 16:57:55 GMT What's Changed

New Contributors

Full Changelog: https://github.com/open-telemetry/opentelemetry.io/compare/2024.11...2024.12

]]>