• EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

Node.js agent release notesRSS

February 12, 2020
Node.js agent v6.4.0

New Features

  • Added support for W3C Trace Context, with easy upgrade from New Relic trace context.

    • Distributed tracing now supports W3C Trace Context headers for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both the W3C trace header format and the New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format.

    • When distributed tracing is enabled with distributed_tracing.enabled: true, the Node agent will now accept W3C's traceparent and tracestate headers when calling TransactionHandle#acceptDistributedTraceHeaders or automatically via http instrumentation. When calling Transaction#insertDistributedTraceHeaders, or automatically via http instrumentation, the Node agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using distributed_tracing.exclude_newrelic_header:true.

    • Added TransactionHandle#acceptDistributedTraceHeaders API for accepting both New Relic and W3C Trace Context distributed traces.

      Deprecated TransactionHandle#acceptDistributedTracePayload which will be removed in a future major release.

    • Added TransactionHandle#insertDistributedTraceHeaders API for adding outbound distributed trace headers. Both W3C Trace Context and New Relic formats will be included unless distributed_tracing.exclude_newrelic_header: true.

      Deprecated TransactionHandle#createDistributedTracePayload which will be removed in a future major release.

    Known issues and workarounds

    • If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Node New Relic agents to this agent release.

Improvements

  • Improved transaction and trace ID generation.

  • AWS Lambda

    • Added collection of additional AWS Lambda event source meta data.
    • Added event type detection for Lambda invocation events.
    • Expanded ARN harvest to include ALB and CloudWatch.

Fixes

  • Fixed issue where Lambda invocation errors were not noticed in Node 10 or Node 12 environments.
  • Pins Node 12 CI/testing version to v12.15 to avoid breakages with v12.16.0 until cause(s) resolved.
  • Updated publish-docs script to use npm run instead of make.

Known issues and workarounds

  • If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Node agents to this agent release.

January 27, 2020
Node.js agent v6.3.0

Improvements

Fixes

  • Fixed spelling in configuration error. Thank you to David Ray (@daaray) for the contribution.
  • Fixed long-log truncation issue in Serverless mode.

November 25, 2019
Node.js agent v6.2.0

New Features

  • Added getLinkingMetadata() method to the API.

    This new method can be used to retrieve the identifying information for the agent and current active span and trace. Please consult the documentation for more information.

  • Added getTraceMetadata() to the agent API.

    This new method can be used to retrieve the current active Distributed Tracing span and trace ids. Please consult the documentation for more information.

  • Added an isSampled() method to Transaction and TransactionHandle.

    This new method can be used to retrieve the sampling decision made for a given transaction. Please consult the documentation for more information.

Fixes

  • Upgraded tap to resolve handlebars audit warnings.

November 5, 2019
Node.js agent v6.1.0

New Features

  • Added @newrelic/aws-sdk module to agent for auto-include on install.
  • Added splitting of application name using semicolons in the env var.
  • Instrumented connection.execute for mysql2.

Improvements

  • @newrelic/native-metrics module is defaulted to disabled in serverless mode.

    This can reduce lambda cold-start times by up to 170ms. The native-metrics module can rarely load in serverless environments due to differences from build environment to deployed environment and offers little value in a serverless environment.

  • Added env var NEW_RELIC_NATIVE_METRICS_ENABLED to enable/disable the native-metrics module

  • Added a test for querying poolCluster.of()

  • Added HTTP method to segment attributes for external requests.

  • Updated the bin/ssl.sh such that it uses verbose output, will exit on first error code, and will refuse to proceed with LibreSSL (which can't generate certs).

  • Added a clear sub-command to bin/ssl.sh that will allow developers to quickly remove generated ssl/cert files and regenerate (useful is switch between platforms via containers/docker and certs needs to be regenerated)

Fixes

  • Removed unused mysql bootstrap test code.
  • Increased timeout for index-bad-version test to reduce flickers on Node 12.
  • Changed file modification to leverage writeFile for watchFile test. This triggers the watcher in a reasonable amount of time much more consistently.
  • Removed testing of Bluebird 3.7 on Node v10 until they fix the segfault issue.

October 29, 2019
Node.js agent v6.0.0

Notes

  • Added official parity support for Node 12.

    • Exception: Errors resulting in unhandled rejections will no longer be scoped to the transaction that was active when the rejected promise was created.

      As of Node 12, the promise responsible for triggering the init async hook will no longer be passed through on the promise wrap instance. This breaks the linkage used to relate a given promise rejection to the transaction it was scheduled in.

  • BREAKING Removed support for Node 6, 7, and 9.

    The minimum supported version is now Node v8. For further information on our support policy, see: https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compa....

    • Bumped version of @newrelic/superagent instrumentation to v2.0.0.
    • Bumped version of @newrelic/native-metrics to v5.0.0.
  • BREAKING Bumped version of @newrelic/koa instrumentation to v3.0.0 @newrelic/koa update includes changes to transaction naming in addition to dropping Node versions 6, 7, and 9. See @newrelic/koarelease notes for what was included in v2.0.0 and v3.0.0 updates. https://github.com/newrelic/node-newrelic-koa/blob/master/NEWS.md.

  • BREAKING max_samples_stored behavior has changed to replace max_samples_per_minute. max_samples_per_minute is no longer a configuration parameter.

    The new behavior for max_samples_stored is as follows: "The agent will collect all events up to this number per minute. If there are more than that, a statistical sampling will be collected." This usage of the configuration is consistent with other New Relic APM agents.

    If your application has previously used max_samples_per_minute as an upper bound, you may need to lower the threshold to a valid maximum to avoid data being dropped on the server. No larger than 10k is recommended.

  • Updated utilization callback test to point to a host that can't represent a valid provider. Previously, location where CI provider runs tests could cause test to fail.

  • Added support for Promise.allSettled() method in Bluebird 3.7.

  • Bumped mongodb dev dependency past security warning.

  • Fixed mongodb versioned tests so they are self-contained by using version under test for setup/teardown instead of agent dev-dependency version.

  • Forced filename resolution if not already cached on module load. This should not occur in normal/non-test scenarios but provides a fall-back to maintain functionality.

  • Refactored restify versioned tests to be less dependent on the order of asynchronous operations.

  • Updated README to reference Pug rather than Jade.

October 10, 2019
Node.js agent v5.13.1

Improvements

  • Added diagnostic code injector.

    The agent may now be configured to make transaction state checks via code injection. This may be turned on by setting code_injector.diagnostics.enabled to true. While this option is enabled, code around async boundaries will be added to track transactions, and log a message when they are not properly reinstated.

  • Added back generation of entity stats logging and uninstrumented support metric generation on metric harvests.

  • Removed legacy harvest code from main agent.

  • Upgraded tap to latest version

  • Upgraded mocha to latest version.

  • Adds --exit flag to mocha test runs to prevent infinite runs on CI.

Fixes

  • primary_application_id now defaults to 'Unknown' in serverless mode to allow Distributed Tracing to function correctly when NEW_RELIC_PRIMARY_APPLICATION_ID is not defined.

  • Updated https-proxy-agent to v3 for security fix.

    Shoutout to @asturur for the contribution.

  • Fixed bug where API.shutdown() would not properly harvest when configured to.

  • Fixed bug where multiple agent restarts would cause the number of 'stopped' listeners to exceed limit.

  • Fixed inconsistent async return from collector API.

    This could result in an infinite loop due to attempting to merge before clearing. This bug should not have impacted normal agent runs but was uncovered for certain test cases.

  • Fixed tests that leave work scheduled on the event loop.

  • Fixed issue that could result in vendor utilization detection failure. As a part of this fix, the request that hits the timeout will immediately abort instead of hanging around for the default timeout.

October 1, 2019
Node.js agent v5.13.0

New Features

  • Support for Real Time Streaming

    • Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation.
    • Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute.
  • Now supports Restify 7 and 8.

  • Distributed Tracing is now enabled by default in serverless mode.

  • HTTPS connections to New Relic now use a keep alive HTTP-Agent.

Improvements

  • Maximum event limits are now enforced by the server. This includes a new maximum of 10000 transaction events per minute.
  • Harvesting is now completed by individually scheduled harvesters per data type.
  • Drops old odd-numbered node versions that are no longer supported by node from travis testing matrix
  • Updated Mocha and Docker links in CONTRIBUTING.md.

Fixes

  • Bumps tap version to move beyond handlebars audit warning.
  • Bumps Restify dev dependency past audit warning.
  • Fixed bug where segment reference on the outbound request was enumerable.
  • Fixed bug where incorrect config information was sent to New Relic.
  • The agent will now end/serialize transactions in the event of an uncaught exception while operating in serverless mode.

July 31, 2019
Node.js agent v5.11.0

New Features

  • Implements Expected and Ignored Errors functionality

  • Adds support for scoped package name introduced in hapi v18 (@hapi/hapi).

    This will provide functionality at parity with instrumentation for hapi v17. Any new features may not yet be supported.

Improvements

  • Bumps jsdoc and lodash dev dependency to avoid upstream vulnerability warning.
  • Adds detailed logging through harvest/collector code to increase supportability.

Fixes

  • Fixed bug where agent would count errors towards error metrics even if they were dropped due to the error collector being disabled.

  • The agent will now properly track cached paths to files in loaded modules on Node versions >10.

    As of Node v11, the path to a file in a module being loaded will only be resolved on the first load; subsequent resolution of that file will use a cached value. The agent records this resolved path and uses it for relative file look ups in order to deep link into modules using Shim#require. Since the agent couldn't reliably get at the path on the subsequent calls to require, it now replicates the caching logic and hold onto the resolved path for a given file.

June 12, 2019
Node.js agent v5.10.0

New Features

  • Enables ability to migrate to Configurable Security Policies (CSP) on a per agent basis for accounts already using High-security mode (HSM).

    When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. high_security has been added as part of the preconnect payload.

Improvements

  • The agent now allows installation on node v11 and v12.

    This change relaxes the engines restriction to include Node v11 and v12. This does not constitute official support for those versions, and users on those versions may run into subtle incompatibilities. For those users who are interested in experimenting with the agent on v11 and v12, we are tracking relevant issues here: https://github.com/newrelic/node-newrelic/issues/279.

Fixes

  • Lambda invocations ended with promises will now be recorded properly.

    Previously, the lambda instrumentation was not intercepting the promise resolution/rejection returned from a lambda handler. The instrumentation now properly observes the promise, and ends the transaction when the promise has finished.

  • Lambda invocations will only attempt to end the related transaction a single time.

    In the event of two lambda response events (e.g. callback called, and a promise returned), the agent would attempt to end the transaction twice, producing an extraneous empty payload. The agent now limits itself to a single end call for a given transaction.

  • The agent will now properly end transactions in the face of uncaught exceptions while in serverless mode.

May 28, 2019
Node.js agent v5.9.1

Improvements

  • Shim#require will now operate as expected.

    Previously, the module interception code made the faulty assumption that a module's filepath would be resolved before the module load call was invoked. This caused the wrap filepath to be attributed to the modules being instrumented. This meant that attempted relative require calls using Shim#require would resolved from the incorrect path. The logic has been changed to keep a stack of the resolved filepaths, resolving the issue.

  • Shim#wrapReturn now uses ES6 proxies to wrap its methods.

    This will accurately propagate look up and assignment onto the underlying wrapped function, while maintaining all previous functionality.

  • Updated versioned test configurations to reflect current engine support.

  • Moved third party notices to THIRD_PARTY_NOTICES.md

  • Updates error message for license check to indicate all places that need to be updated.

Copyright © 2024 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.