open-telemetry/opentelemetry-js experimental/v0.222.0

on GitHub

0.222.0

💥 Breaking Changes

• fix(sdk-node)!: fail-fast on Propagator creation from config file #6930 @trentm
• fix(sdk-node)!: fail-fast on MeterProvider creation from config file #6954 @trentm
• fix(sdk-node)!: fail-fast on TracerProvider creation from config file #6962 @trentm
• fix(sdk-node)!: fail-fast on Resource creation from config file #6989 @trentm

  • 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"

🚀 Features

• feat(sdk-logs): deprecate SdkLogRecord in favor of ReadWriteLogRecord #6939 @pichlermarc

🐛 Bug Fixes

• fix(instrumentation-http): redact sensitive query parameters on incoming (server) spans; add redactedQueryParamsServer config option @dyladan
• fix(sdk-node): support headers_list when creating OTLP exporters from declarative configuration #6953 @JacksonWeber

📚 Documentation

• docs(sdk-logs): mark logger configuration as experimental #6996 @LarryHu0217
• docs(configuration): document the ConfigModel suffix naming convention for exported types #6612 @vedantchalke36

🏠 Internal

• refactor(sampler-jaeger-remote): remove axios dependency and use fetch to get the sampler configuration from Jaeger API #6963 @david-luna