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

Node.js agent release notesRSS

April 2, 2015
Node.js agent v1.18.1

Notes

  • Names assigned to errors via Error.name now appear in the UI.

    Previously, the name of an error in the UI appeared as Error.constructor.name or with a default of Error. Now the common pattern of Error.name is respected and takes precedence.

  • Child segments of external calls will now be nested correctly.

    This change causes segments that make up external calls to nest under the call correctly. Previously, the child segments appeared as siblings to external calls.

  • The request_uri attribute on errors will now only include the path without any parameters.

    This behavior now matches the other New Relic agents.

March 27, 2015
Node.js agent v1.18.0

Notes

  • Reduce agent CPU overhead by omitting setImmediate from traces.

    The change to setImmediate makes that function behave the same way as nextTick and other frequently-called functions that are already elided from Transaction Traces.

  • Mitigate a Node.js memory leak that can occur during TLS connections.

    There is an outstanding Node.js Core memory leak involving TLS connections. Clients specifying certificates, such as the New Relic Agent, quickly reveal this leak. We now mitigate this issue by using the default client certificates where possible. A new log message will be printed when the TLS memory leak workaround can not be used, such as when using a custom certificate with an HTTPS proxy.

March 19, 2015
Node.js agent v1.17.3

Notes

  • Fixed a bug where external requests report times longer than the transactions that initiated them. External request segments are now always ended when an error occurs.
  • Fixed a bug that produced incorrect transaction names for some routes in express2 and express3.

March 12, 2015
Node.js agent v1.17.2

Notes

  • Fixed a bug that interfered with listing the routes in Express apps.
  • Fixed a bug that caused custom transaction names to appear as "unknown".
  • Added more log detail when instrumentation fails to load.

March 5, 2015
Node.js agent v1.17.1

Notes

  • Added instrumentation support for Node.js PostgreSQL driver pg 4.x.
  • Added instrumentation support for Datastax's Cassandra driver.
  • Updated Oracle instrumentation to collect new datastore metrics.

February 25, 2015
Node.js agent v1.17.0

Notes

  • Added instrumentation for modules in Node core.

  • Added support for native Promises in Node.js 0.12 and io.js 1.x.

  • Traces will now contain separate segments for async waits and callbacks.

  • Updated instrumentation for MongoDB to support previously un-instrumented methods for 1.x and 2.x versions of the node-mongodb-native driver.

  • Fixed a bug in the recording of transaction metrics. Previously this would cause a duplicate of the transaction metric to be displayed in the transaction breakdown chart

  • Unified view for SQL database and NoSQL datastore products.

    The response time charts in the application overview page will now include NoSQL datastores, such as Cassandra and MongoDB,and also the product name of existing SQL databases such as MySQL, Postgres, Oracle, etc. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores, such as Cassandra and MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases.

    This new unified Databases page will enable the filtering of metrics and operations by product, and includes a table listing all operations.

    Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the agent version on all hosts. If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views.

February 20, 2015
Node.js agent v1.16.4

Notes

  • Fixed a bug in the logger to respect the configured log level in all cases.

Node.js agent v1.16.3

Notes

  • Fixed a bug in hapi 8 view segments. Previously, the segments weren't being ended when the view ended.
  • Added a configuration option to completely disable logging. logger.enabled defaults to true, if set to false it won't try to create the log file.

February 13, 2015
Node.js agent v1.16.2

Notes

  • Enable http/https proxy features on all supported Node versions.

    Supported versions: Node.js 0.8, 0.10, 0.12 and io.js 1.x.

  • Fixed a bug in vhost detection in Hapi 8. This bug would result in a crash for users of vhosts.

February 6, 2015
Node.js agent v1.16.0

Notes

  • Added support for synthetic monitoring transaction tracing.

    Synthetic monitoring lets you monitor your site from around the world. When you use synthetics to monitor your Node application, up to 20 detailed transaction traces will now be captured every minute when the application is probed from synthetics. To learn more about this feature, visit our documentation.

Copyright © 2024 New Relic Inc.

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