Releases: open-telemetry/opentelemetry-js
Releases ยท open-telemetry/opentelemetry-js
v1.25.1
1.25.1
๐ (Refine Doc)
- refactor(examples): added usage of @opentelemetry/semantic-conventions and @opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @Zen-cronic
๐ (Internal)
- refactor(context-zone-peer-dep): use explicit exports #4785 @pichlermarc
- refactor(context-async-hooks): use explicit exports #4785 @pichlermarc
experimental/v0.52.1
0.52.1
๐ (Enhancement)
- refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
- refactor(otlp-transformer): use explicit exports #4785 @pichlermarc
๐ (Bug Fix)
- fix(sdk-node): register context manager if no tracer options are provided #4781 @pichlermarc
- fix(instrumentation): Update
import-in-the-middle
to fix numerous bugs #4806 @timfish - chore(instrumentation): Use a caret version for
import-in-the-middle
dependency #4810 @timfish
๐ (Internal)
- test: add
npm run maint:regenerate-test-certs
maintenance script and regenerate recently expired test certs #4777
v1.25.0
1.25.0
๐ (Enhancement)
- feat: support node 22 #4666 @dyladan
- feat(context-zone*): support zone.js 0.12.x #4376 @maldago
- refactor(core): Use tree-shakeable string constants for semconv #4739 @JohannesHuster
- refactor(shim-opentracing): Use tree-shakeable string constants for semconv #4746 @JohannesHuster
- refactor(sdk-trace-web): Use tree-shakeable string constants for semconv #4747 @JohannesHuster
- refactor(sdk-trace-node): Use tree-shakeable string constants for semconv #4748 @JohannesHuster
- refactor(sdk-trace-base): Use tree-shakeable string constants for semconv #4749 @JohannesHuster
- refactor(resources): update deprecated semconv to use exported strings #4755 @JamieDanielson
- refactor(exporters): update deprecated semconv to use exported strings #4756 @JamieDanielson
๐ (Refine Doc)
- refactor(examples): use new exported string constants for semconv in examples/esm-http-ts #4758 @Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/basic-tracer-node #4759 @Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/http #4750 @Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/grpc-js #4760 @Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/otlp-exporter-node #4762 @Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/opentracing-shim #4761 @Zen-cronic
experimental/v0.52.0
0.52.0
๐ฅ Breaking Change
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
@opentelemetry/otlp-transformer
#4542 @pichlermarc- Breaking changes:
- (user-facing)
convert()
now returns an empty object and will be removed in a follow-up - (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
- (internal) OTLPExporterNodeBase now has an additional
ResponseType
type parameter
- (user-facing)
- Breaking changes:
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
@opentelemetry/otlp-transformer
#4581 @pichlermarc- Breaking changes:
- (user-facing)
convert()
has been removed from all exporters - (internal) OTLPExporterBrowserBase:
RequestType
has been replaced by aResponseType
type-argument - (internal) OTLPExporterNodeBase:
ServiceRequest
has been replaced by aServiceResponse
type-argument - (internal) the
@opentelemetry/otlp-exporter-proto-base
package has been removed, and will from now on be deprecated innpm
- (user-facing)
- Breaking changes:
- feat(instrumentation): remove default value for config in base instrumentation constructor #4695: @blumamir
- fix(instrumentation)!: remove unused supportedVersions from Instrumentation interface #4694 @blumamir
- feat(instrumentation)!: simplify
registerInstrumentations()
API- Breaking changes:
- removes
InstrumentationOptions
type - occurrences of
InstrumentationOptions
are now replaced by(Instrumentation | Instrumentation[])[]
- migrate usages of
registerInstrumentations({instrumentations: fooInstrumentation})
toregisterInstrumentations({instrumentations: [fooInstrumentation]})
- passing Instrumentation classes to
registerInstrumentations()
is now not possible anymore.
- migrate usages of
- removes
- Breaking changes:
- feat(sdk-node)!: simplify type of
instrumentations
option- Breaking changes:
- replaces
InstrumentationOptions
with(Instrumentation | Instrumentation[])[]
- replaces
- Breaking changes:
๐ (Enhancement)
- feat(instrumentation): apply unwrap before wrap in base class #4692
- feat(instrumentation): add util to execute span customization hook in base class #4663 @blumamir
- feat(instrumentation): generic config type in instrumentation base #4659 @blumamir
- feat: support node 22 #4666 @dyladan
- feat(propagator-aws-xray-lambda): add AWS Xray Lambda propagator 4554
- refactor(instrumentation-xml-http-request): use exported strings for semantic attributes. #4681
๐ (Bug Fix)
- fix(instrumentation): Update
import-in-the-middle
to fix numerous bugs #4745 @timfish
๐ (Refine Doc)
api/v1.9.0
1.9.0
๐ (Enhancement)
- feat(metrics): added synchronous gauge #4528 @clintonb
- feat(api): allow adding span links after span creation #4536 @seemk
- This change is non-breaking for end-users, but breaking for Trace SDK implmentations in accordance with the specification as new features need to be implemented.
- feat: support node 22 #4666 @dyladan
v1.24.1
1.24.1
๐ (Bug Fix)
- fix(core): align inconsistent behavior of
getEnv()
andgetEnvWithoutDefaults()
when aprocess
polyfill is used #4648 @pichlermarcgetEnvWithoutDefaults()
would useprocess.env
if it was defined when running in a browser, whilegetEnv()
would always use_globalThis
. Now both use_globalThis
when running in a browser.
- fix(resources): prevent circular import (resource -> detector -> resource -> ...) #4653 @pichlermarc
- fixes a circular import warning which would appear in rollup when bundling
@opentelemetry/resources
- fixes a circular import warning which would appear in rollup when bundling
- fix(exporter-metrics-otlp-grpc): add explicit otlp-exporter-base dependency to exporter-metrics-otlp-grpc #4678 @AkselAllas
Experimental v0.51.1
0.51.1
๐ (Bug Fix)
- fix(instrumentation): update import-in-the-middle to 1.7.4
v1.24.0
1.24.0
๐ (Enhancement)
- feat(sdk-trace-base): log resource attributes in ConsoleSpanExporter #4605 @pichlermarc
- feat(propagator-aws-xray): moved AWS Xray propagator from contrib 4603 @martinkuba
- feat(resources): new experimental detector ServiceInstanceIdDetectorSync that sets the value for
service.instance.id
as random UUID. #4608 @maryliag
๐ (Bug Fix)
Experimental v0.51.0
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 insteadNodeSDK.configureMeterProvider()
, please use constructor options insteadNodeSDK.configureLoggerProvider()
, please use constructor options insteadNodeSDK.addResource()
, please use constructor options insteadNodeSDK.detectResources()
, this is not necessary anymore, resources are now auto-detected onNodeSDK.start()
if the constructor optionautoDetectResources
is unset,undefined
ortrue
.
- 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
- breaking for instrumentation authors that depend on
๐ (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 variableOTEL_NODE_RESOURCE_DETECTORS
, e.gOTEL_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
- merging a resource containing the
- The resource detector can be added to default resource detector list by adding the value
๐ (Bug Fix)
- fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @pichlermarc
- fix(instrumentation): Don't use
require
to loadpackage.json
files #4593 @timfish
v1.23.0
1.23.0
๐ (Enhancement)
- perf(sdk-trace-base): do not allocate arrays if resource has no pending async attributes #4576 @Samuron
- feat(sdk-metrics): added experimental synchronous gauge to SDK #4565 @clintonb
- this change will become user-facing in an upcoming release
๐ (Bug Fix)
- fix(sdk-metrics): increase the depth of the output to the console such that objects in the metric are printed fully to the console #4522 @JacksonWeber