Breaking change to sdk.start()! Previously start returned a promise, and users were encouraged to load their application code when the promise resolved. Improvements have been made to the NodeSDK package to make start synchronous. This allows users to setup tracing in a separate file that can be required using node -r. See the readme and example for further details.
OpenTelemetry dependencies have been upgraded to API v1.4.1, core v1.10.1 and auto-instrumentations-node v0.36.4.

1.3.0

published 1.3.0 • 2 years ago

Changelog

OpenTelemetry dependencies have been upgraded to API v1.3.0, core v1.8.0, with auto-instrumentations-node v0.35.0.
Support for the recently GA'd metrics SDK has been added. This functionality is opt-in and users will need to set metricsEnabeld: true in code, or via the environment by setting LS_METRICS_ENABLED=true. Refer to the README for all metrics related configuration options.

1.2.0

published 1.2.0 • 2 years ago

Changelog

This release changes the default export format for launcher from OTLP/JSON to OTLP/proto (e.g. proto over HTTP). Aside from the change in export format, this release is identical to v1.1.0. Users wishing to use OTLP/JSON can use v1.1.0 and transition to a vanilla OpenTelemetry SDK setup moving forward.

published 1.1.0 • 2 years ago

Changelog

This release requires microsatellite version 2022-10-03_20-16-42Z or later as it addresses backwards incompatible changes to OTLP/JSON that were introduced in OTLP v0.15. Note, the next release of launcher (v1.2.0) will change its export format from OTLP/JSON to OTLP/proto.
OpenTelemetry dependencies have been updated to the latest available: API v1.2.0, core v1.7.0 and instrumentations v0.33.1.
telemetry.distro.name and telemetry.distro.version are now recorded as resource attributes.