New features
Error totals are now reported.
The agent now reports metrics that reflect the total number of errors that have occurred in web and background transactions.
Bug fixes
Disabling SSL no longer requires the setting of a port.
Previously, the agent required changing
port
in the config to80
when disabling SSL. The agent will now default to port 80 if a port is not supplied and SSL is turned off.Logging functions have been improved.
The agent will now properly log error stack traces and can rate limit logging messages. To aid in debugging we have provided more logging about the public API.
New features
Advanced Analytics for APM Errors
With this release, the agent reports TransactionError events. These new events power the Advanced Analytics for APM Errors feature. The error events are also available through New Relic Insights.
Advanced Analytics for APM Errors lets you see all of your errors with granular detail, filter and group by any attribute to analyze them, and take action to resolve issues through collaboration.
Bug fixes
NEW_RELIC_LOG_ENABLED
environment variable is now treated as a boolean.Previously, this option was treated as a string, causing it to not work for some use cases. Thanks to @jakecraige for contributing this fix!
Notes
newrelic.getBrowserTimingHeader()
API now includes the full transaction name.Previously, the agent would use a fragment of the transaction name, causing Browser Monitoring transactions and APM transactions to not be cross linked. This change makes the cross linking work correctly.
Notes
The New Relic Node Agent now officially supports Node v4!
We are excited to announce that the New Relic Node Agent officially supports Node v4.x! We've tested the agent across all major versions of Node used by New Relic customers to ensure a quality Node APM experience. New Relic recommends upgrading to Node v4.x for best Node Agent performance.
Corrected a parsing issue in the slow sql query parsing step.
Previously, the agent would not be able to parse inputs to database libraries that specified sql as an option param. This was an issue with node-mysql, namely. The agent now correctly handles this case and registers the queries as expected.
Notes
Removed client support of the RC4 stream cipher for communicating with the New Relic servers.
The RC4 cipher is considered unsafe and is generally being deprecated.
Fix for logging version number in Express instrumentation. Thanks @tregagnon.
When an unsupported version of Express is detected, we log a message that contains the Express version number. The version is a string and was being logged as a number, resulting in NaN in the log message.
Agent is now more safe when recording memory stats.
Previously, the agent would crash the process as it was gathering memory usage information (i.e. when process.memoryUsage threw an error). This defect is now guarded against with a try-catch.
Notes
Express and Connect instrumentation will no longer crash on Node 4
As of ES6, the
Function.name
attribute will track if the function is a getter/a setter/is bound to (i.e.fn.bind().name ->
'bound ' + fn.name
). This new behavior caused the agent to crash on start up due to the way connect and express are instrumented. The agent is now more defensive of future implementations of ES6.
Notes
Errors will now respect its transaction's ignore state.
When ignoring transactions, related errors will now also be ignored.
The agent can now handle immutable and frozen error objects.
In rare cases the agent gets passed an immutable error object. The agent would then crash when trying to tag the error object with the current transaction. We now handle these errors properly.
Notes
Corrected a defect in the handling of uncaught exceptions
This defect was surfaced in versions of node that did not have
process._fatalException
, namely v0.8. When an uncaught exception occurs, the agent now records the error and passes it along to the other uncaught exception handlers that have been registered. This was inverted before, passing along errors when there were no other error handlers present and rethrowing otherwise.
Notes
Moved
concat-stream
from dev dependencies to production dependencies.Last week we released v1.21.0 but forgot to move a dependency. We've removed v1.21.0 from npmjs.org and this release contains the changes from that version.
Support for display host names (originally in 1.21.0).
The agent now has configuration settings to allow configuration of custom host names. Set
process_host.display_name
to enable this.If this config is not set, the agent will continue to use the host name found through an
os.hostname()
call. Should this lookup fail somehow,process_host.ipv_preference
can now be set to4
or6
to configure the type of ip address displayed in place of the host name.
Notes
This release has been unpublished from npmjs.org. Use v1.21.1 or higher instead.
Support for display host names.
The agent now has configuration settings to allow configuration of custom host names. Set
process_host.display_name
to enable this.If this config is not set, the agent will continue to use the host name found through an
os.hostname()
call. Should this lookup fail somehow,process_host.ipv_preference
can now be set to4
or6
to configure the type of ip address displayed in place of the host name.