• EnglishEspañol日本語한국어Português
  • 로그인지금 시작하기

Node.js agent release notesRSS

October 20, 2016
Node.js agent v1.32.0

New features

  • The agent now collects database instance information for MySQL and MongoDB operations. This information (database server and database name) is displayed in transaction traces and slow query traces.
  • Datastore instance configuration can now be done through environment variables. These can be set through NEW_RELIC_DATASTORE_INSTANCE_REPORTING_ENABLED and NEW_RELIC_DATASTORE_DATABASE_NAME_REPORTING_ENABLED

Bug fixes

  • The agent will no longer crash the process when an express param handler is executed when a transaction is not active.

October 12, 2016
Node.js agent v1.31.0

New features

  • The agent now collects database instance information for PostgreSQL and Redis operations. This information (database server and database name) is displayed in transaction traces and slow query traces.

October 4, 2016
Node.js agent v1.30.5

Bug fixes

  • Fixed issue with aborted requests causing the agent to crash in some cases.

    Previously the agent would crash when the client request aborted before Express server sent a response and encountered an error.


  • Upgraded integration tests to work with the latest version of node-tap.

September 27, 2016
Node.js agent v1.30.4


  • Fixed format of external calls metric.

    External service URLs will now be formatted the same as they are in the originating application.

  • Improved instrumentation of native promises.

    Native promises now use the same instrumentation as Bluebird, making instrumentation easier to maintain and more consistent across libraries.

Bug fixes

  • Fixed issue with reloading normalization rules from the server.

    Upon reset, the agent will clear the existing naming rules, removing any vestigial rules that may have changed or been disabled.

  • Fixed issue with key transactions Apdex metric.

    Key transactions now effect the global Apdex metric according to their own ApdexT instead of the default ApdexT value.

  • Fixed issue with closing transactions when the request is aborted.

    Previously, aborted requests would result in the transaction remaining open indefinitely. Now the transaction will be correctly finished and its resources freed.

September 16, 2016
Node.js agent v2.1.1-beta


  • Incorporated fixes from v1.30.1, v1.30.2, and v1.30.3.

September 14, 2016
Node.js agent v1.30.3


This release is the same as v1.30.2 except it has been published using npm 2 to make sure all nested bundled dependencies are included.

September 13, 2016
Node.js agent v1.30.2



This release has been unpublished from npmjs.org. Please use version 1.30.3 or higher.

New features

  • Added instrumentation of the param() function in Express.

    The agent will now create metrics and transaction segments when the Express param() function is called as a part of a route. This also fixes an issue with transaction naming when the HTTP response is ended within a param() method.

Bug fixes

  • Fixed an issue with naming Express transactions that result in 404 errors.

    Previously transactions were not always correctly normalized for URLs that caused 404 errors. The transactions will now always be reported with the same normalized name (e.g. "get /").

  • Fixed instrumentation of Express v4.0 - v4.5.

    Previously transactions were not correctly named on older versions of Express 4.


  • Minor upates to logging.

September 1, 2016
Node.js agent v1.30.1

Bug fixes

  • The shutdown method is now on the stub API.

    Previously when the agent was disabled the stub API passed back on require did not have the shutdown method. Thanks goes to Vlad Fedosov (@StyleT) for this contribution!

  • Global timers will now be wrapped correctly regardless of being wrapped by something else.

    The logic to check whether to wrap the global timers was looking to see if the global timers were the same function reference as the ones in the timers module. This would break in cases where either the global or timers functions had been wrapped.

  • Director instrumentation now correctly handles the case of null route handlers being passed in.

    Previously the agent's director instrumentation would crash in cases of null route handlers in director.

August 29, 2016
Node.js agent v2.1.0-beta


You must read and agree to the Beta Agreement before using this beta version of the agent.

New features

  • Added rowCallback property to datastore segment descriptors.

    With this parameter the shim will record the given function/parameter as a per-row callback which may be called multiple times. These calls will be counted up for traces.


  • Incorporated fixes from v1.30.0

  • Rewrote PostgreSQL instrumentation using new DatastoreShim class.

  • Reversed reverse_naming_rules default.

    Naming rules now default to evaluating in forward order.

August 25, 2016
Node.js agent v1.30.0

New features

  • A number of improvements and fixes to transaction naming rules.

    Added attributes terminate_chain, replace_all, and precedence to allow more control over how naming rules are executed. Please see the updated documentation in our README file.

    The order in which naming rules are executed can now be reversed with a feature flag reverse_naming_rules.

    When applying naming rules, the regular expression matching is now case insensitive.

    We have added a tool for testing naming rules. When the agent is installed, the tool can be run in terminal by executing node node_modules/.bin/newrelic-naming-rules.

    We have also improved our trace logging around transaction naming.


  • Added trace logging to track number of transactions and segments in progress, and to better track segments created with the Express instrumentation.
  • Fixed mysql2 tests that were not being run correctly.

Bug fixes

  • Fixed issue with reporting errors from domains.

    When an error is handled by using the error event of the domain, it is no longer reported as an uncaught exception.

Copyright © 2024 New Relic Inc.

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