Node.js agent release notesRSS

Notes

• Improved the Express instrumentation to be more defensive before doing property lookups, fixing a crash that could happen in an exceptional state.
• Improved logging when the New Relic agent cannot connect to New Relic servers.
• Make Cross Application Tracer header injection less aggressive fixing interaction with other libraries such as riak-js.

Notes

• Added support for Hapi v8.
• briandela contributed a fix for an crash that would occur when using hapi with vhosts.

Fixes

• Fixed a bug that caused some outbound http requests to show up in the New Relic UI as requests to localhost rather than the specified domain.
• The agent no longer reports errors from outbound http requests if they were handled by the user's application

Notes

• The node agent now instruments connections to Oracle Databases using the oracle driver. This patch was contributed by ryanwilliamquinn
• Fixed an issue that would break kraken apps when the node agent was enabled. This patch was contributed by Lenny Markus

Notes

Added support for the the aggregate method on mongodb collections. This patch was contributed by taxilian

Notes

• Fixed a bug in Cross Application Tracing where the agent would sometimes attempt to set a header after headers had already been sent.

• Replaced the logger with one that is handles file writes properly lowering overall resource usage.

  This is a small change with a large impact. fs.createWriteStream returns whether data was queued or not. If it is queued it is recommended to wait on a drain event but this isn't mandatory. Most loggers we've found ignore this event which leads to many writes getting buffered and a rapid increase in native heap size as well as lowering the process's ability to respond to requests.

Notes

• Updated support for hapi 7.2 or higher.

  Hapi refactored how the server is instantiated and caused the agent to not be able to get transaction names. This release accounts for the update and enables full instrumentation.

Notes

• This release was unpublished from npm due to a bad merge

Notes

• Added support for Custom Metrics

  Custom metrics provides a way to send additional metrics up to New Relic APM, which can be viewed with Custom Dashboards. We have two APIs for this, recordMetric(name, value) and incrementMetric(name[, value]). Read more about Node.js custom metrics.

• Fixed a bug in deeply nested transactions.

  Previously we allowed transactions to be nested to any depth. We've found in some cases this causes stack depth problems and are now limiting to 900 segments per transaction. We will still collect metrics on all segments, but transaction traces will only show the first 900.

• Fixed a bug where custom tracers would show 0 time if the transaction ended n them.

  This may change the times you see for other types of tracers by a small amount. The change will reflect slightly more accurate timing.