semconv.com

Specificationv1.53.0

since v1.52.0
2 breaking7 notable13 editorial

From the upstream release notes

Read the full release notes

Breaking2

Requirements added to, removed from, or restrengthened in a document marked Stable.

  • rule droppedrequirementlogs/data-model.md#type-mapstring-anyMUST removed: The implementation MUST by default ensure that the exported maps contain only unique keys.
  • rule droppedrequirementlogs/data-model.md#type-mapstring-anyMUST removed: If such option is provided, it MUST be documented that for many receivers, handling of maps with duplicate keys is unpredictable and it is the users' responsibility to ensure keys are not duplicate.

Notable7

  • removedsectionlogs/data-model.md#definitions-used-in-this-documentSection "Definitions Used in this Document" removed.
  • removedsectionlogs/data-model.md#type-anySection "Type any" removed.
  • removedsectionlogs/data-model.md#type-mapstring-anySection "Type map<string, any>" removed.
  • strengthrequirementconfiguration/sdk.md#createSHOULD strengthened to MUST: If a property is required, and not present, Create MUST return an error.
  • new rulerequirementlogs/api.md#ergonomic-apiMAY added: Languages MAY additionally provide a more ergonomic and convenient logging API.
  • new rulerequirementlogs/api.md#ergonomic-apiSHOULD added: The ergonomic API SHOULD make it more convenient to emit event records following the event semantics.
  • new rulerequirementlogs/api.md#ergonomic-apiSHOULD added: The design of the ergonomic API SHOULD be idiomatic for its language.

Editorial13