Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
- Fixed an issue where collected errors did not include captured and custom parameters.
- Added the environment variable
NEW_RELIC_HIGH_SECURITY. This correlates to thehigh_securitysetting in yournewrelic.jsfor High-security mode.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
Client side setting of
high_securityis 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: trueto 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.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
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.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
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}
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
On connect, the full
newrelicmodule 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.jsfile depending on server-side, and environmental configuration.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
Express 4 support.
Express 4 apps now have their transactions named correctly. Errors in the middleware chain are properly recorded.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
- Fix issue where dangling symbolic links in the
node_modulesfolder would crash the environment scraper.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
- Upgrade continuation-local-storage dependency to 3.0.0. The
newrelicnode module usesclsto help join asynchronous transaction segments. The latestclsmodule includes a fix that prevents contexts from leaking across transactions.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
- Add high-security compliance for accounts with enterprise security enabled. By default, the agent now works with high-security accounts, whereas previously agents would receive an
Access Violation. - Add a
.addCustomParameter(name, value)api call for adding custom parameters to transaction traces, and extend the.noticeError(error, customParameters)for adding additional parameters to error traces. - Documentation fix in the
README.mdfor ignoringsocket.ioroutes. - Better support for disabling browser timing headers server side. Previously the agent would not pick up the server change until restart. The agent will now disable browser timing headers as soon as the next harvest cycle.
- Fix a
socket hangup errorthat was causing some agents to fail to handshake with the New Relic servers.
Important
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
- Browser monitoring! Real User Monitoring! Which is also known as RUM! Whatever it's called, it allows you to see how long your pages take to load, not just on the server side, but in the browser! Wow! It's super cool! We know a lot of you have been waiting for this, and it's here! It's manually set up with an API call! Check the README for details!
- By default, all communication between New Relic for Node and New Relic's servers is now protected with crisp, clean TLS encryption. To minimize the CPU overhead of running connections over SSL (and it can be configured, see the README and the online documentation for details on how to return to plain HTTP), New Relic for Node is now using a keep-alive connection that will properly pipeline connections, for both HTTP and HTTPS.
- Improved the timings for a large class of MongoDB / Mongoose use cases. If you've encountered the issue where MongoDB trace segments last for an absurdly long duration, this should help.