Skip to content

@elastic/opentelemetry-node 1.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Apr 21:06
· 530 commits to main since this release
v1.0.0
00a9811
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changelog

  • BREAKING CHANGE: Change the default behavior of logging framework
    instrumentations (for Bunyan, Pino, and Winston), to not do "log sending"
    by default. "Log sending" is the feature name of
    @opentelemetry/instrumentation-bunyan,
    @opentelemetry/instrumentation-pino, and
    @opentelemetry/instrumentation-winston
    to send log records directly to the configured OTLP collector. The new
    default behavior effectively sets the default config for these
    instrumentations to {disableLogSending: true}.

    This default behavior differs from the current default in OpenTelemetry JS.
    OpenTelemetry Java instrumentation docs
    provide an argument for why log sending (or "Direct to collector") should be
    opt-in. A common workflow for applications is to log to file or stdout and
    have some external process collect those logs. In those cases, if the
    OpenTelemetry SDK was also sending logs directly, then the telemetry
    backend would very likely have duplicate logs.

    This is controlled by the ELASTIC_OTEL_ENABLE_LOG_SENDING environment variable.
    To enable log-sending by default, set ELASTIC_OTEL_ENABLE_LOG_SENDING=true.
    (#680)

  • BREAKING CHANGE: Set default value of OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE to delta.
    This change is done to follow the recommendations specified in the EDOT docs.
    (#670)

  • feat: Default to stable semantic conventions for HTTP instrumentation.
    (#669)

  • Upgrade upstream OTel dependencies to SDK 2.0. This should be non-breaking
    for users of node --import @elastic/opentelemetry-node my-app.js to start
    EDOT Node.js for their application.
    (#663)

  • BREAKING CHANGE: Remove support for passing in a function for a particular
    instrumentation to the getInstrumentations() utility. It wasn't adding any
    value.

  • chore: Use peerDependencies for @opentelemetry/api dep, and cap it to a
    known-supported maximum version, according to OTel JS guidance for
    implementors
    (#606)

  • BREAKING CHANGE: Remove the @elastic/opentelemetry-node/sdk entry-point for the 1.0.0 release.
    This will be brought back in a minor release. It is being removed so that the
    exported API can be re-worked to be more supportable.

  • BREAKING CHANGE: Temporarily remove the 'gcp' resource detector, due to an
    issue
    that results in misleading tracing data from the resource detector appearing
    to be from the application.
    (#703)

README | Full Changelog

Assets 2
Loading