0.212.0
💥 Breaking Changes
- feat(sdk-logs)!: move environment variable configuration to
@opentelemetry/sdk-node#6325 @pichlermarc- (user-facing): environment variable configuration is no longer applied automatically when instantiating SDK components
(LoggerProvider,BatchLogRecordProcessor) directly from@opentelemetry/sdk-logs. Please migrate to using
NodeSDKfrom@opentelemetry/sdk-nodeto get automatic environment variable configuration.
- (user-facing): environment variable configuration is no longer applied automatically when instantiating SDK components
🚀 Features
- feat(configuration): add Prometheus exporter support #6400 @MikeGoldsmith
- feat(sampler-composite): add ComposableAnnotatingSampler and ComposableRuleBasedSampler #6305 @trentm
- feat(configuration): parse config for rc 3 #6304 @maryliag
- feat(instrumentation): use the
internals: trueoption with import-in-the-middle hook, allowing instrumentations to hook internal files in ES modules #6344 @trentm
🐛 Bug Fixes
- fix(configuration): remove default propagator initialization #6399 @MikeGoldsmith
- fix(instrumentation-fetch): preserve Response.url, type, and redirected properties #6243 @AnubhavPurohit691
- The fetch instrumentation now preserves the read-only
url,type, andredirectedproperties from the original Response object when wrapping it with a Proxy. This fixes issues where code relying on these properties (e.g., CORS type detection) would fail with instrumented fetch.
- The fetch instrumentation now preserves the read-only
- fix(exporter-prometheus): add missing
@opentelemetry/semantic-conventionsdependency #6330 @omizha - fix(otlp-transformer): correctly handle Uint8Array attribute values when serializing to JSON #6348 @pichlermarc
- fix(otlp-exporter-base): fix unwanted instrumentation of the fetch exports when context is not propagated #6353 @david-luna
🏠 Internal
- perf(otlp-transformer): optimize toAnyValue performance #6287 @AbhiPrasad