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

Experimental v0.51.0

on GitHub

0.51.0

💥 Breaking Change

• feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @pichlermarc
  • NodeSDK.configureTracerProvider(), please use constructor options instead
  • NodeSDK.configureMeterProvider(), please use constructor options instead
  • NodeSDK.configureLoggerProvider(), please use constructor options instead
  • NodeSDK.addResource(), please use constructor options instead
  • NodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected on NodeSDK.start() if the constructor option autoDetectResources is unset, undefined or true.
• feat(instrumentation): add patch and unpatch diag log messages #4641
  • Instrumentations should not log patch and unpatch messages to diag channel.
• feat!(instrumentation): remove moduleExports generic type from instrumentation registration #4598 @blumamir
  • breaking for instrumentation authors that depend on
    • InstrumentationBase
    • InstrumentationNodeModuleDefinition
    • InstrumentationNodeModuleFile

🚀 (Enhancement)

• refactor(instrumentation-grpc): move to use SEMATTRS #4633
• feat(otlp-transformer): consolidate scope/resource creation in transformer #4600
• feat(sdk-logs): print message when attributes are dropped due to attribute count limit #4614 @HyunnoH
• feat(sdk-node): add usage for the detector ServiceInstanceIdDetectorSync. #4626 @maryliag
  • The resource detector can be added to default resource detector list by adding the value serviceinstance to the list of resource detectors on the environment variable OTEL_NODE_RESOURCE_DETECTORS, e.g OTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstance
  • The value can be overwritten by
    • merging a resource containing the service.instance.id attribute
    • using another resource detector which writes service.instance.id

🐛 (Bug Fix)

• fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @pichlermarc
• fix(instrumentation): Don't use require to load package.json files #4593 @timfish