fix(deps): update dependency newrelic to v10 - autoclosed #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.16.0
->10.6.2
Release Notes
newrelic/node-newrelic (newrelic)
v10.6.2
Compare Source
v10.6.2 (2023-08-07)
Bug Fixes
Miscellaneous Chores
Tests
Support statement:
We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/)
See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)
v10.6.1
Compare Source
Security Improvements
Support statement:
We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/)
See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)
v10.6.0
Compare Source
Miscellaneous Chores
Continuous Integration
Support statement:
We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/)
See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)
v10.5.0
Compare Source
Features
Bug Fixes
Miscellaneous Chores
Support statement:
v10.4.2
Compare Source
v10.4.2 (2023-07-13)
Bug Fixes
request.uri
attribute when obfuscating (#1719) (76112a6)Miscellaneous Chores
Tests
Support statement:
v10.4.1
Compare Source
Security Improvements
Miscellaneous Chores
Support statement:
v10.4.0
Compare Source
Miscellaneous Chores
Continuous Integration
Build System
@newrelic/aws-sdk
to latest to get the instrumentation fixes for 3.363.0 (#1707) (a2cca08)Support statement:
v10.3.2
Compare Source
v10.3.2 (2023-06-26)
Bug Fixes
Security Improvements
Miscellaneous Chores
Support statement:
v10.3.1
Compare Source
v10.3.1 (2023-06-22)
Security
Miscellaneous Chores
Support statement:
v10.3.0
Compare Source
Features
config.security.agent.enabled
is true. (#1664) (3e926e5)NOTE: The security agent IAST mode is in public preview and should only be used in non-production environments.
config.security.agent.enabled
andconfig.security.enabled
to true.Support statement:
v10.2.0
Compare Source
v10.2.0 (2023-06-06)
Features
Added supportability metrics to indicate how agent was loaded and if source maps were enabled (#1657) (6f6f7e6)
Supportability/Features/CJS/Preload
- recorded if-r newrelic
was used to load agentSupportability/Features/CJS/Require
- recorded ifrequire('newrelic')
was used to load agentSupportability/Features/EnableSourceMaps
- recorded ifnode --enable-source-maps
was present to start applicationAdded logging of
process.execArgs
at the debug level (#1654) (c85c006)Miscellaneous Chores
Tests
Support statement:
v10.1.2
Compare Source
Bug Fixes
PoolNamespace.prototype.query
Continuous Integration
Support statement:
v10.1.1
Compare Source
v10.1.1 (2023-05-15)
Bug Fixes
Code Refactoring
SKIP_C8
env var to the job. (#1621) (0ba9dcb)Documentation
Miscellaneous Chores
Tests
Continuous Integration
Support statement:
v10.1.0
Compare Source
Added batching and compression to infinite tracing.
config.infinite_tracing.compression
tofalse
.config.infinite_tracing.batching
tofalse
.NEW_RELIC_INFINITE_TRACING_BATCHING
andNEW_RELIC_INFINITE_TRACING_COMPRESSION
.Added support to record Nest.js error stack traces.
Added job to create a release notes PR in the post-release workflow.
Removed request library and updated helper to use http/https to make requests in tests.
Reduced cognitive complexity in lib/serverless/aws-lambda.js
Support statement:
v10.0.0
Compare Source
v10.0.0 (2023-04-19)
BREAKING - Updated the default of
config.transaction_tracer.record_sql
fromoff
toobfuscated
. This means that sql statements will be captured but obfuscated.BREAKING - Route (URL) parameters are now stored as
request.parameters.route.*
attributes on Transactions, root Segments and Spans.After this change, the following becomes true:
Query parameters will be available as attributes prefixed with request.parameters.* on Transactions and Spans.
Route parameters will be available as attributes prefixed with request.parameters.route.* on Transactions and Spans.
Route parameters (aka url parameters) are a common feature of various web frameworks, where you can create a placeholder as part of an API route definition.
For example, given the following Express route definition and request url:
curl http://localhost:3000/api/users/abc123?id=true
The route parameter is
id
, and has a value ofabc123
. This would becomerequest.parameters.route.id: abc123
on the Transaction, root Segment, and Span attributes. This example also has a query parameter ofid
, which has a value of true. This would becomerequest.parameters.id: true
on the Transaction, root Segment, and Span attributes.BREAKING - Removed
captureUrlParams
fromWebFrameworkShim
class.DEPRECATION NOTICE:
shim.unwrap
andshim.unwrapOnce
will no longer function if you attempt to unwrap an item that has been wrapped multiple times.shim.unwrap
andshim.unwrapOnce
in the next major release.Added the ability to register instrumentation multiple hooks (onRequire, onResolved) for the same resolved moduleName.
api.instrument
,api.instrumentDatastore
,api.instrumentWebframework
,api.instrumentMessages
, orapi.instrumentConglomerate
, it would override existing instrumentation hooks. The effect was that the Node.js agent would not function as designed.Refactored lib/transaction/tracecontext.js to reduce cognitive complexity.
Refactored lib/transaction/trace/index.js to reduce cognitive complexity.
Upgraded devDependencies jsdoc, and lean-jsdoc-theme.
Support statement:
v9.15.0
Compare Source
heroku.use_dyno_names
to specify whether or not to useprocess.env.DYNO
for naming the host name and display host. This option defaults to true. If you are on heroku and do not want this functionality setheroku.use_dyno_names
tofalse
. You can also control this configuration options with the environment variable ofNEW_RELIC_HEROKU_USE_DYNO_NAMES
. Thanks @benney-au-le for your contribution 🚀Support statement:
v9.14.1
Compare Source
__NR_cache
instead of a symbol to properly detect attempts at loading agent twice.Support statement:
v9.14.0
Compare Source
setErrorGroupCallback
, which provides a way for you to customize theerror.group.name
attribute of errors that are captured by the agent. This attribute controls how the Errors Inbox functionality groups similar errors together. To learn more about this function, please refer to our example app.Support statement:
v9.13.0
Compare Source
Updated http instrumentation to no longer remove the
x-new-relic-disable-dt
header when using AWS SDK v3. This was done to prevent the "The request signature we calculated does not match the signature you provided. Check your key and signing method." error from AWS SDK.Added an API method
setUserID
to provide an ability to associate a unique identifier with a transaction event, transaction trace and errors within transaction. The attribute will beenduser.id
.Added default configuration for security agent.
Support statement:
v9.12.1
Compare Source
v9.12.1 (2023-03-15)
Added ability to mark errors as expected when using
newrelic.noticeError
, by adding an optional boolean:newrelic.noticeError(error, {customAttributes}, true|false)
when there are custom error attributes.newrelic.noticeError(error, true|false)
if there are no custom error attributes.expected
errors do not affect error metrics or Apdex.Added ability to disable distributed tracing for aws-sdk >= 3.290.0.
Updated README header image to latest OSS office required images
updated @grpc/grpc-js from 1.8.8 to 1.8.9
Support statement:
v9.12.0
Compare Source
v9.11.0
Compare Source
v9.11.0 (2023-03-08)
@prisma/client
).@prisma/client
is 4.0.0.$queryRaw
,$executeRaw
,$queryRawUnsafe
, and$executeRawUnsafe
the names will be aligned with the raw SQL.(i.e. Datastore/statement/Prisma/User/select)Huge shoutout to @osmanmrtacar for the original contribution 🙏🏻
@grpc/protoloader
from 0.7.4 to 0.7.5.@grpc/grpc-js
from 1.8.7 to 1.8.8.Support statement:
v9.10.2
Compare Source
v9.10.2 (2023-02-21)
request.aborted
withresponse.close
in HTTP instrumentation.NEW_RELIC_GRPC_IGNORE_STATUS_CODES
was not properly parsing the codes as integers, thus not ignoring reporting errors of certain status codes.@grpc/grpc-js
from 1.8.4 to 1.8.7.Support statement:
v9.10.1
Compare Source
Support statement:
v9.10.0
Compare Source
v9.10.0 (2023-02-09)
Exposed a method on API to obfuscate sql:
newrelic.obfuscateSql
.Add support for Multi Value Parameters from API Gateway and ALB events for Lambdas (Thank you @Engerim for your contribution 🙏🏻)
Support statement:
v9.9.0
Compare Source
v9.9.0 (2023-02-06)
Added support for url obfuscation using regex (Thanks for your contribution @matewilk)
path
will be obfuscatedrequest.url
attribute will be obfuscatedhttp.uri
path will be obfuscatedurl
will be obfuscated/api/v1/users/12345456/edit
to/api/v1/users/**/edit
.Add a new tracking type of instrumentation. This will be responsible for logging
Supportability/Features/Instrumentation/OnResolved/<pkg>
andSupportability/Features/Instrumentation/OnResolved/<pkg>/Version/<version>
metrics when packages are required.Support statement:
v9.8.1
Compare Source
v9.8.1 (2023-01-25)
Changed GCP metadata parsing to use
json-bigint
to avoid loss of precision from numerical instance ID.Instrumented
winston.loggers.add
so it works likewinston.createLogger
.Support statement:
v9.8.0
Compare Source
v9.8.0 (2023-01-17)
getBrowserTimingHeader
to allow Browser Agent to be generated even when not in a Transaction by addingallowTransactionlessInjection
to function options.allowTransactionlessInjection
is a boolean option, and when set totrue
, will allow injection of the Browser Agent when not in a transaction. This is intended to be used in frameworks that build Static Site Generation(SSG). Note that if you are using this option, you may need to wait until the Node agent has established a connection before callinggetBrowserTimingHeader
. To wait until the agent is connected, you can add the following check to your code:Support statement:
v9.7.5
Compare Source
Added a check to the code level metrics utility to ensure filePath was set before adding the
code.*
attributes.Updated to latest version of
@newrelic/test-utilities
Fixed issue where listing of dependencies and packages from symlinked nested directories created an infinite loop which caused the agent to never connect.
Support statement:
v9.7.4
Compare Source
/proc
information.Support statement:
v9.7.3
Compare Source
v9.7.3 (2022-12-12)
startSegment
,startBackgroundTransaction
, andstartWebTransaction
.Support statement:
v9.7.2
Compare Source
@grpc/grpc-js
instrumentation to work with 1.8.0.Support statement:
v9.7.1
Compare Source
v9.7.1 (2022-12-06)
Reintroduced throttling during reading of instrumented application's dependency tree during startup, to prevent EMFILE issues.
Improved Restify support
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:
v9.7.0
Compare Source
grpc.ignore_status_codes
, which can be used to select nonzero gRPC status codes to ignore and not report as errors.Support statement:
v9.6.0
Compare Source
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.
NEW_RELIC_PATH_TO_CONFIG_KEY
.config.nested.object_path.enabled
the env var would beNEW_RELIC_NESTED_OBJECT_PATH.ENABLED
.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:
v9.5.0
Compare Source
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 documentation 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 document for our current feature flags.
Support statement:
v9.4.0
Compare Source
v9.4.0 (2022-10-24)
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
Note: If you are including a serialized error make sure it is on the
error
key of the log event: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.
config.feature_flag.async_local_context
NEW_RELIC_FEATURE_FLAG_ASYNC_LOCAL_CONTEXT=1
Support statement:
v9.3.0
Compare Source
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:
v9.2.0
Compare Source
v9.2.0 (2022-10-06)
Added ability to instrument ES Modules with the New Relic ESM Loader.
Added support for custom ESM instrumentation.
api.esm.custom_instrumentation_entrypoint
newrelic.instrument*
methods will still work exceptnewrelic.instrumentLoadedModule
. This is because it is geared toward CommonJS modules.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:
v9.1.0
Compare Source
Added experimental loader to support instrumentation of CommonJS packages in ECMAScript Module(ESM) applications.
16.12.0
.Enhanced supportability metrics for ESM support.
Supportability/Features/ESM/Loader
andSupportability/Features/ESM/UnsupportedLoader
).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:
v9.0.3
Compare Source
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:
v9.0.2
Compare Source
v9.0.2 (2022-08-23)
Exposed
compressed_content_encoding
configuration and defaulted it to "gzip".Added a special case to serialize BigInts when sending them to New Relic. BigInts can appear in log data that our customers may be trying to forward.
Added unit test suite for
lib/logger.js
.Added destructive integration test for Configuration instantiation.
Fixed public jsdoc generation.
Added
minami
back as a dev dependency for use withjsdoc-conf.js
.Support statement:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.