Node.js agent release notesRSS

Improvements

• PostgreSQL support via the `pg` driver.

  The Node.js agent now records the amount of time spent in transactions with PostgreSQL databases. This timing can be viewed in the Transactions page within individual transactions and their traces.

  The agent supports all of the following `pg` usage scenarios:

  • Using the pure javascript API exposed directly from `pg`
  • Using the "native" API exposed from `pg.native`
  • Using the "native" API exposed directly from `pg` when the `NODE_PG_FORCE_NATIVE` environment variable is set
  • Using the pure javascript API from the `pg.js` module

Fixes

• Removed a preemptive DNS lookup of the New Relic servers that could cause errors when behind a proxy.

Fixes

• Fix to prevent proxy credentials transmission

  This update prevents proxy credentials set in the agent config file from being transmitted to New Relic.

Improvements

• MySQL Pooling Support

  Better support for mysql pooling, including connections that use createPoolCluster and createPool. Previously connections obtained through a pool could potentially be uninstrumented.

Notes

• Custom instrumentation

  The agent now allows you to annotate your application code to provide customized instrumentation. This includes the ability to time both web and background transactions, and add tracers to measure activity within transactions like querying a database. For more information, see custom instrumentation

Fixes

• Fixed a bug in the express instrumentation where if you named an error handler function handle it would cause a recursion depth error.

• Added a check for invalid characters in the app_name setting.

  The agent will now emit a warning and disable itself if any application name is invalid. Allowed characters are alphanumerics and certain punctuation characters ({}.?!')

• Router queue time now properly handles floating point values.

• Fixed a bug where a socket connection could throw a synchronous error and cause the application to crash.

• We now support Cassandra via the node-cassandra-cql driver.

  New database instrumentation means that we can present you with the timing data for how long those queries take. Thanks to Aaron Silvas from GoDaddy for the initial implementation of the Cassandra instrumentation.

• Router queue time now supports t=<number> in the X-REQUEST-START and X-QUEUE-START headers.

Notes

• Agent now tracks metrics for router queue time. In addition to X-REQUEST-START, the agent now supports X-QUEUE-START header times. This metric will show up as "Request Queueing" in the Overview tab.