Node.js agent release notesRSS

• Fixed a bug where mutibyte characters would cause an error when sending data to the New Relic servers.

Notes

• Updated hapi instrumentation to support the recently released v6.9.

• Fixed a bug where an invalid package.json could cause the agent to crash while it recursed through node_modules gathering version details.

• Properly name other SQL queries.

  Previously when the agent failed to parse SQL it would create a metric stating the database type, query type, and query table were all unknown. This has been changed to keep track of database type and create an appropriate other operation metric like other agents.

Notes

• Custom Instrumentation functions now pass through the return value of their passed in callback.

• Multiple improvements to PostgreSQL instrumentation

  When no callback was detected in the query functions, we were inserting our own. The insertion itself caused a crash. Adding a callback also modified the behavior of the pg module. Instead, we now listen for error or end events to finish segments.

  We now generate metrics for statement type/table combinations. Look for these in the database tab your APM Account!

Fixes

• Improved MongoDB find instrumentation.

  The mongo driver provides many ways to invoke its API and find documents. In previous releases, some API invocations would create transaction trace segments that would not end properly, leading to inaccurately large segment times. This release ensures the agent always instruments finding and iterating through documents, ensuring segment times are accurate.

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