Skip to content
semconv.com
↑↓ move↵ openUse with your agent →

Specificationv1.62.0

since v1.61.0
22 breaking28 notable45 editorial

From the upstream release notes

Read the full release notes

Breaking22

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

Notable28

  • removedsectionresource/sdk.md#detecting-resource-information-from-the-environmentSection "Detecting resource information from the environment" removed.
  • new rulerequirementconfiguration/sdk.md#createSHOULD added: warn and skip: Create SHOULD generate a warning identifying the unrecognized name and gracefully ignore the reference.
  • new rulerequiremententities/data-model.md#entity-data-modelMUST added: This field is required and MUST not be empty for valid entities. | | Schema URL | string | Identifies the schema version for the entity's attributes.
  • new rulerequirementmetrics/sdk.md#shutdown-2MUST added: Shutdown MUST include the effects of ForceFlush.
  • new rulerequirementresource/sdk.md#entitiesSHOULD added: SHOULD be detected synchronously during SDK initialization.
  • new rulerequirementresource/sdk.md#entitiesMAY added: MAY change over the lifetime of the entity.
  • new rulerequirementresource/sdk.md#entitiesMAY added: A Resource MAY contain zero or more entities.
  • new rulerequirementresource/sdk.md#entity-aware-resource-detectorsSHOULD added: Resource detectors SHOULD produce resources with entities attached.
  • new rulerequirementresource/sdk.md#resource-detectorSHOULD added: Empty Schema URL SHOULD be used if the detector does not populate the resource with any known attributes that have a semantic convention or if the detector does not know what attributes it will populate (e.g. the detect...
  • new rulerequirementresource/sdk.md#resource-detectorMAY added: Resource detector packages MAY also return (Development) Entities alongside resource attributes.
  • new rulerequirementresource/sdk.md#resource-detectorSHOULD added: Entity-aware resource detectors SHOULD detect entity attributes synchronously.
  • new rulerequirementresource/sdk.md#resource-detectorMAY added: Entity attributes MAY be detected asynchronously (e.g. via a future or promise that resolves after initialization).
  • new rulerequirementresource/sdk.md#resource-detectorMAY added: Unresolved attributes MAY be represented as asynchronous values.
  • new rulerequirementresource/sdk.md#resource-providerMAY added: Detectors MAY run concurrently.
  • new rulerequirementtrace/sdk.md#shutdownSHOULD added: Shutdown SHOULD also invoke Shutdown on the configured Sampler, if supported.
  • new rulerequirementtrace/sdk.md#shutdown-1SHOULD added: The Sampler interface SHOULD provide a Shutdown method.
  • new rulerequirementtrace/sdk.md#shutdown-1SHOULD added: Samplers that delegate to other samplers, such as ParentBased and AlwaysRecord, SHOULD invoke Shutdown on each delegate that supports it.
  • new rulerequirementtrace/sdk.md#shutdown-1SHOULD NOT added: Repeated or concurrent calls to Shutdown SHOULD NOT repeat cleanup.
  • new rulerequirementtrace/sdk.md#shutdown-1SHOULD NOT added: Callers, including TracerProvider, SHOULD NOT call ShouldSample after Shutdown begins.
  • new rulerequirementtrace/sdk.md#shutdown-1SHOULD added: If such a call occurs, implementations SHOULD return DROP without executing their sampling logic.
  • new rulerequirementtrace/sdk.md#shutdown-1MAY added: Samplers that always return a static sampling decision MAY continue returning that decision.
  • new rulerequirementtrace/sdk.md#shutdown-1MAY added: Calls to ShouldSample already in progress MAY complete with their normal result.
  • new rulerequirementtrace/sdk.md#shutdown-2SHOULD added: Shutdown SHOULD be called only once for each SpanProcessor instance.
  • new rulerequirementtrace/sdk.md#shutdown-2SHOULD added: Shutdown SHOULD provide a way to let the caller know whether it succeeded, failed or timed out.
  • new rulerequirementtrace/sdk.md#shutdown-2SHOULD added: Shutdown SHOULD complete or abort within some timeout.
  • new rulerequirementspecification/versioning-and-stability.md#security-related-changesMAY added: Stable SDK and Contrib components MAY make backward-incompatible behavioral changes, change configuration defaults, or restrict supported configuration values without incrementing the major version when necessary to add...
  • new rulerequirementspecification/versioning-and-stability.md#security-related-changesMAY added: Such changes MAY be released as security fixes in a patch release, subject to the support requirements in this document.
  • new rulerequirementspecification/versioning-and-stability.md#security-related-changesSHOULD added: Where safe and feasible, implementations SHOULD provide a configuration override or other migration path.

Editorial45