@opentelemetry/api-logs

:boom: Breaking Changes

• breaking

  web-common: clean up and deprecate network span utils #7114

  • These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.

  • Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents().

:boom: Breaking Changes

• breaking

  sdk-node: fail-fast on Propagator creation from config file #6930

• breaking

  sdk-node: fail-fast on MeterProvider creation from config file #6954

• breaking

  sdk-node: fail-fast on TracerProvider creation from config file #6962

• breaking

  sdk-node: fail-fast on Resource creation from config file #6989

  • This also breaks some usage of startNodeSDK() for environment-based config, i.e. when not using a config file. For example with OTEL_NODE_RESOURCE_DETECTORS=all, it results in an error message and a no-op SDK.
    (This does not impact users of new NodeSDK() -- the currently recommended mechanism to start an SDK using this package.)

    Could not create OpenTelemetry SDK from configuration, SDK will not be setup: unknown ExperimentalResourceDetector name in configuration: "container"

:rocket: Features

• deprecated

  sdk-logs: deprecate SdkLogRecord in favor of ReadWriteLogRecord #6939

:bug: Bug Fixes

• instrumentation-http: redact sensitive query parameters on incoming (server) spans; add redactedQueryParamsServer config option @dyladan

• sdk-node: support headers_list when creating OTLP exporters from declarative configuration #6953