Node.js agent release notesRSS

The agent now reports the value of the NODE_ENV environment variable to New Relic.

This will show up in your Settings -> Environment tab in APM. The data is being collected for debugging and to aid support.

Captured parameters for express, restify, and hapi have been normalized.

When capture_params is enabled the agent will collect route and query parameters. Previously express and restify only captured route params, and hapi only captured query params. This normalizes the behavior across the frameworks.

Fixed an issue with restify instrumentation that caused the agent to always collect route parameters.

Users of restify who want to continue capturing route (and now query) parameters are advised to enable capture_params.

Fixed an issue where circular configs caused the agent to crash.

Client side setting of high_security is now supported.

High-security mode is a feature to prevent any sensitive data from being sent to New Relic. The local setting for the agent must match the server setting in the New Relic APM UI. If there is a mismatch, the agent will log a message and act as if it is disabled. A link to the docs for High-security mode can be found here

Attributes of high-security mode (when enabled):

• requires ssl
• does not allow capturing of parameters,
• does not allow custom parameters

The default setting for High-security mode is ‘false’.

Note: If you currently have high-security mode enabled within the New Relic APM UI, you have to add high_security: true to your local newrelic.js.

Fixed a bug in our instrumentation of restify, where if you were using the restify client with express as a web server, req.query would be overridden.

New Relic Insights support no longer requires a feature flag. If you are a paying customer, you'll begin to see data show up in Insights as soon as you upgrade to 1.6.0. The agent will send event data for every transaction up to 10,000 per minute. After that events are statistically sampled. Event data includes transaction timing, transaction name, and any custom parameters. You can read what is sent in more detail here.

You can read more about Insights here. Documentation for configuring this feature can be found here.

Fix a bug where if the user disabled the error collector, error count would be carried over harvest cycles instead of reset. This would result in an ever increasing error count until the app was restarted.

New Relic Insights beta support. This is a feature for our paying customers. The support of Insights in the agent is beta, this means we don't recommend turning the feature on in production, but instead trying it out in development and staging environments.

To enable Insights support add the following to your newrelic.js:

feature_flag : {
insights: true
}

On connect, the full newrelic module configuration is pushed to New Relic APM. Full config will be visible under the Agent initialization tab, under the Settings button in the APM application page.

The reported settings will reflect the running agent config, which may differ from the newrelic.js file depending on server-side, and environmental configuration.

Express 4 support.

Express 4 apps now have their transactions named correctly. Errors in the middleware chain are properly recorded.