중요
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
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.
중요
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
- This release was unpublished from npm due to a bad merge
중요
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
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.
중요
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.
- Fixed a bug that would cause the application to crash on outbound connections when using node 0.8.
- Fixed a bug that could sometimes cause the application to crash while parsing MySQL queries.
중요
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
Added support for Label Categories
The agent now supports setting Labels for your application on a per instance level, using either an environment variable, or a config file setting. https://docs.newrelic.com/docs/apm/new-relic-apm/maintenance/categories-...
Improved transaction names for express 4
express 4 added the ability to mount apps and routers at specific urls. The node agent would previously use only the portion of the route that was the last router or app matched as the transaction name. Transaction names will now include the entire matched route.
Added detection for uninstrumented instances of modules that should be instrumented
The agent will now detect if an application has required a module before
require('newrelic')
.If this occurs, the agent will add a warning in the log file and display a warning banner in the UI.Added more logging to custom instrumentation APIs at
debug
level.The logging was improved for the benefit of people using the following APIs:
createTracer
,createWebTransaction
,createBackgroundTransaction
, andendTransaction
. It will log when transactions are created and when transactions are ended. It will also log when it can't create a tracer due to there being no active transaction.Fixed a bug in PostgreSQL instrumentation where the event emitter from
query
could not chain.on
calls. This patch was contributed by sebastianhoitz.Fixed a bug in
createBackgroundTransaction
where if the agent was disabled it didn't take agroup
argument. This patch was contributed by nullvariable.Fixed a bug in our URL parsing where in Node v0.11.14
url.parse
returns a differently shaped object than expected. This patch was contributed by atomanticNote: Node v0.11.x is not officially supported, but Node v0.12 will be and this patch helps us get ready for that.
중요
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
Added support for Cross Application Tracing
The agent now supports Cross Application Tracing, which allows the New Relic APM UI to display traces that span multiple applications.
Fixed a bug that would cause application to crash on request when using the kraken framework.
Loosened the restrictions on the
app_name
setting. Application names may now include any Unicode characters.
중요
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.
Fixes
Fixed a type error while checking payload size before reporting to New Relic.
When this occurred the agent would fail to send the payload to New Relic. This was more likely to occur in high throughput applications.
중요
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.
- Fixed a bug where mutibyte characters would cause an error when sending data to the New Relic servers.
중요
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
Updated hapi instrumentation to support the recently released v6.9.
Fixed a bug where an invalid package.json could cause the agent to crash while it recursed through
node_modules
gathering version details.Properly name
other
SQL queries.Previously when the agent failed to parse SQL it would create a metric stating the database type, query type, and query table were all unknown. This has been changed to keep track of database type and create an appropriate
other
operation metric like other agents.
중요
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
Custom Instrumentation functions now pass through the return value of their passed in callback.
Multiple improvements to PostgreSQL instrumentation
When no callback was detected in the query functions, we were inserting our own. The insertion itself caused a crash. Adding a callback also modified the behavior of the pg module. Instead, we now listen for
error
orend
events to finish segments.We now generate metrics for statement type/table combinations. Look for these in the database tab your APM Account!