Node.js agent release notesRSS

New features

• The agent now collects database instance information for Memcached operations.

  This information (database server and database name) is displayed in transaction traces and slow query traces.

Improvements

• socket.io long-polling requests are now ignored by default.

  Collecting metrics for these requests is typically not desirable since they are frequent and do not represent business transactions. Previously we recommended adding an ignore rule manually. Now it is included by default.

• Improved test coverage for Postgres and MongoDB instrumentations.

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.

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.

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.

Improvements

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

Improvements

• 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.

Improvements

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

Notes

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.

Notes

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.

Improvements

• Minor upates to logging.

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.