Notes
- Updated
@grpc/grpc-js
instrumentation to work with 1.8.0.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Reintroduced throttling during reading of instrumented application's dependency tree during startup, to prevent EMFILE issues.
Improved Restify support
- Added a new test stanza to run restify >=10 on Node 18.
- Update our versioned tests to support Restify 9.0.0.
Laid foundation for supporting Code Level Metrics via CodeStream. Note that this integration is not fully finished and should not be used.
Improved the readability and maintainability of agent by reducing the Cognitive Complexity of various aspects of the agent.
Added
newrelic.noticeError()
example to our API docs.Upgraded @grpc/grpc-js from 1.6.9 to 1.7.3.
Upgraded @grpc/proto-loader from 0.6.13 to 0.7.3.
Removed async from benchmark tests, fixed failing benchmark suites, and removed deprecated suite.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
- Added new configuration option,
grpc.ignore_status_codes
, which can be used to select nonzero gRPC status codes to ignore and not report as errors.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Dropped support for
vision
, and instead only instrument@hapi/vision
.Updated configuration system to automatically create an environment variable mapping for a new config value.
- It will follow a convention of
NEW_RELIC_PATH_TO_CONFIG_KEY
. - For example if there is a new configuration option of
config.nested.object_path.enabled
the env var would beNEW_RELIC_NESTED_OBJECT_PATH.ENABLED
.
- It will follow a convention of
Removed
transaction_tracer.hide_internals
configuration. All of the internal configuration is now handled by Javascript symbols instead of non-enumerable properties, so there is no longer a performance penalty, as symbols are already hidden by default.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Increased the default limit of custom events from 1,000 events per minute to 3,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for custom_insights_events. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post.
Updated CI process to include collection of code coverage statistics.
Added a [doc about our current feature flags)(https://github.com/newrelic/node-newrelic/blob/main/documentation/feature-flags.md).
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Removed legacy agent async context propagation. The default behavior is now what was behind the
feature_flag.new_promise_tracking
. You can read more about the difference here.Fixed an issue with the ES Module loader that properly registers instrumentation when the file path included url encoded characters.
Added an API for enqueuing application logs for forwarding
newrelic.recordLogEvent({ message: 'hello world', level: 'info' })`Note: If you're including a serialized error make sure it's on the
error
key of the log event:const error = new Error('testing errors');newrelic.recordLogEvent({ message: 'error example', level: 'error', error })Fixed
cassandra-driver
instrumentation to properly set instance details on query segments/spans.Added a new context manager that leverages AsyncLocalStorage for async context propagation.
- This will be available via a feature flag
config.feature_flag.async_local_context
- Alternatively you can set the environment variable of
NEW_RELIC_FEATURE_FLAG_ASYNC_LOCAL_CONTEXT=1
- By enabling this feature flag it should make the agent use less memory and CPU.
- This will be available via a feature flag
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Added instrumentation to bunyan to support application logging use cases: forwarding, local decorating, and metrics. Big thanks to @brianphillips for his contribution
Added c8 to track code coverage.
Added documentation about custom instrumentation in ES module applications
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Added ability to instrument ES Modules with the New Relic ESM Loader.
Added support for custom ESM instrumentation.
- There is structure to registering custom ESM instrumentation. Set the relative path to the instrumentation entry point via
api.esm.custom_instrumentation_entrypoint
- Sample custom ESM instrumentation entrypoint
- All the
newrelic.instrument*
methods will still work exceptnewrelic.instrumentLoadedModule
. This is because it is geared toward CommonJS modules.
- There is structure to registering custom ESM instrumentation. Set the relative path to the instrumentation entry point via
Added test for asserting ESM loader functionality on ESM-only package
Added supportability metric of
Supportability/Nodejs/Collector/MaxPayloadSizeLimit/<endpoint>
whenmax_payload_size_in_bytes
configuration value is exceeded.Removed
application_logging.forwarding.enabled
stanza from sample config as the feature is now enabled by default.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Added experimental loader to support instrumentation of CommonJS packages in ECMAScript Module(ESM) applications.
- It only supports versions of Node.js >=
16.12.0
. - It is subject to change due to its experimental stability.
- It only supports versions of Node.js >=
Enhanced supportability metrics for ESM support.
- Added new metrics to track usage of ESM loader(
Supportability/Features/ESM/Loader
andSupportability/Features/ESM/UnsupportedLoader
). - Updated instrumentation map to include an optional "friendly name" for tracking metrics.
- Added new metrics to track usage of ESM loader(
Enabled re-throwing ESM import errors of
newrelic.js
so that the user is informed to rename it tonewrelic.cjs
Fixed an issue with mongodb instrumentation where IPv6 address([::1]) was not getting mapped to localhost when setting the host attribute on the segment.
Added a test ESM loader to properly mock out agent in versioned tests.
Added ESM versioned tests for:
express
,pg
,mongodb
, and@grpc/grpc-js
.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
Notes
Updated gRPC client instrumenation to respect
grpc.record_errors
when deciding to log errors on gRPC client requests.Fixed transaction name finalization to properly copy the appropriate transaction name to root segment.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.