Express instrumentation has been fundamentally reworked.
This refactor includes a few bug fixes around error handling and transaction naming, as well as optional higher resolution traces.
feature_flag.express_segments to true in the agent config will make the agent report the amount of time spent in each individual middleware per request
The agent will not report errors handled in an error handler it is monitoring - this is more in line with how the agent does error handling in other contexts.
The agent will now name transactions correctly when an application responds from a middleware.
Added instrumentation of Bluebird promises.
Previously, the transaction state could get lost when multiple promises resolved close to each other.
Fixed issue with PostgreSQL native instrumentation.
require('pg').nativemore than once was causing the agent to crash.
Fixed issue with hapi instrumentation not returning value from Server.connection().
Various improvements to tests to make them more stable.
Added more HTTP request/response parameters to transactions.
The agent now collects additional request/response HTTP headers (e.g. contentType, HTTP method, response status code). These can be used to filter and group errors in the Error analytics page, as well as events in Insights.
- Fixed an issue with collecting errors when an Express error handler removed message and stack properties from the error object.
Added Q instrumentation.
The node agent now accurately records programs using Q for promises.
Thanks to @mdlavin for the contribution!
Added node-mysql2 support.
Thanks to @jhollingworth for adding node-mysql2 support to the agent.
Query streaming in node-mysql now works while using the agent.
Previously, due to the way node-mysql was instrumented query streaming would be forced off when the agent was collecting data. This is no longer the case and query streaming will work and be recorded as expected.
Added support for the new Response Time Line and better representation of asynchronous data.
This has many implications in the UI. The first is the Application Overview, in the past we've always just shown "node" and maybe "request queueing" on the response time graph. We now show you an application breakdown like our other language agents! This means you'll be able to see how much time was in HTTP externals, your various datastores, or spent in node itself. Overlaid on this will be your response time as a blue line.
Next page that has been affected is our Transaction Overview page. Specifically when you click into a Transaction to see more detail. Previously we showed you a breakdown of the top time consumers in that transaction, both as a graph and as a table. Unfortunately that graph didn't show response time and the table would show percentages over 100%. Now, like the Application Overview, you will get a blue response time line and the breakdown table will have numbers that add up much more intuitively!
Finally, our Transaction Trace view has also been updated. The change is very similar to the changes mentioned above for the breakdown table in the Transaction Overview page. You should no longer see percentages over 100% here either.
Transaction trace serialization is now 4x faster than before.
This speedup will primarily affect those with large, deeply nested transactions. Though small transactions have seen some improvement as well.
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.
Disabling SSL no longer requires the setting of a port.
Previously, the agent required changing
portin the config to
80when 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.
Advanced Analytics for APM Errors
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.
NEW_RELIC_LOG_ENABLEDenvironment 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!