[Snyk] Upgrade newrelic from 5.2.1 to 5.13.1 #5
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.
Snyk has created this PR to upgrade newrelic from 5.2.1 to 5.13.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.The recommended version fixes:
SNYK-JS-HTTPSPROXYAGENT-469131
Release notes
Package name: newrelic
restart/disconnected event
listener limit
Added back generation of entity stats logging and uninstrumented support metric
generation on metric harvests.
Fixed inconsistent async return from collector API. This could result in an
infinite loop due to attempting to merge before clearing. This bug should not
have impacted normal agent runs but was uncovered for certain test cases.
Removed legacy harvest code from main agent.
Updated to v3.
Shoutouts to @asturur for the contribution.
Added diagnostic code injector.
The agent may now be configured to make transaction state checks via code
injection. This may be turned on by setting
to . While this option is enabled, code around async boundaries will be added
to track transactions, and log a message when they are not properly reinstated.
Fixed bug where would not properly harvest when configured to.
now defaults to 'Unknown' in serverless mode to allow
Distributed Tracing to function correctly when is not defined.
Upgrades to latest version
Bumps to latest version.
Fixes tests that leave work scheduled on the event loop.
Adds flag to mocha test runs to prevent infinite runs on CI.
Fixed issue that could result in vendor utilization detection failure.
As a part of this fix, the request that hits the timeout will immediately abort
instead of hanging around for the default timeout.
Bumps dev dependency past audit warning.
Decouples metric harvest into own standalone scheduled aggregator.
Drops old odd-numbered node versions that are no longer supported by node from
travis testing.
Updated the transaction trace aggregator to handle sending its data autonomously.
Decouples Transaction event harvest into own standalone scheduled aggregator.
versioned test skips nest SDK version as it has a crashing bug. Resumes
with the next version assuming there will be a fix.
Decouples custom event harvest into own standalone scheduled aggregator.
Changed, added, and removed tests to instrument Restify 7.
Decouples error trace and error event harvests into own standalone scheduled
aggregators.
Distributed Tracing is now enabled by default in serverless mode.
Made the segment reference on the outbound request non-enumerable.
server. These are not valid to receive. Fixed tests and added cleanup to
better isolate some test failures.
exception while operating in serverless mode.
NEW_RELIC_ERROR_COLLECTOR_EXPECTED_CODES, NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERRORS
ENV vars for new ignore and expected error configuration values
Implements the ignore_messages and ignore_classes configuration values, allowing
the agent to completely ignore certain errors
Adds server side configuration boilerplate for ,
, , , and
code
Bumps lodash minimum dev dependency to get past most recent vulnerability.
Added support for scoped package name introduced in hapi v18 (@hapi/hapi).
This will provide functionality at parity with instrumentation for hapi v17. Any
new features may not yet be supported.
Huge shoutout to Aori Nevo (@aorinevo) for this contribution.
Updated development deps to clear known security vulnerabilities.
Shoutouts to Aori Nevo (@aorinevo) for this contribution.
Fixed bug where agent would count errors towards error metrics even if they were
dropped due to the error collector being disabled.
functionality to the error collector, allow users to report errors that will not
impact the error counts or apdex
The agent will now properly track cached paths to files in loaded modules on Node
versions >10.
As of Node v11, the path to a file in a module being loaded will only be resolved
on the first load; subsequent resolution of that file will use a cached value.
The agent records this resolved path and uses it for relative file look ups in
order to deep link into modules using . Since the agent couldn't
reliably get at the path on the subsequent calls to require, it now replicates
the caching logic and hold onto the resolved path for a given file.
Adds detailed logging through harvest/collector code to increase supportability.
The agent now allows installation on node v11 and v12.
This change relaxes the engines restriction to include node v11 and v12. This does
not constitute official support for those versions, and users on those versions
may run into subtle incompatibilities. For those users who are interested in
experimenting with the agent on the v11 and v12, we are tracking relevant issues
here: #279.
Lambda invocations ended with promises will now be recorded properly.
Previously, the lambda instrumentation was not intercepting the promise
resolution/rejection returned from a lambda handler. The instrumentation now
properly observes the promise, and ends the transaction when the promise has
finished.
Lambda invocations will only attempt to end the related transaction a single time.
In the event of two lambda response events (e.g. callback called, and a promise
returned), the agent would attempt to end the transaction twice, producing an
extraneous empty payload. The agent now limits itself to a single end call for
a given transaction.
The agent will now properly end transactions in the face of uncaught exceptions
while in serverless mode.
Enables ability to migrate to Configurable Security Policies (CSP) on a per agent
basis for accounts already using High Security Mode (HSM).
When both HSM and CSP are enabled for an account, an agent (this version or later)
can successfully connect with either or the appropriate
configured. has been added as part of
the preconnect payload.
moved third party notices to
Shim#require will now operate as expected.
Previously, the module interception code made the faulty assumption that a module's
filepath would be resolved before the module load call was invoked. This caused
the wrap filepath to be attributed to the modules being instrumented. This meant
that attempted relative require calls using Shim#require would resolved from the
incorrect path. The logic has been changed to keep a stack of the resolved
filepaths, resolving the issue.
Updates error message for license check to indicate all places that need to be
updated.
Shim#wrapReturn now uses ES6 proxies to wrap its methods.
This will accurately propagate look up and assignment onto the underlying wrapped
function, while maintaining all previous functionality.
Updated versioned test configurations to reflect current engine support.
null
Modifies route property to allow functions and defers route
processing and segment naming until just before needed (each middleware
invocation).
Fixed outdated ref in .
Middleware instrumentation now honors spec.appendPath for more cases and will
not pop paths when it has not appended a path.
Added to .
Now web transactions will be named after known status code messages (404, 405,
and 501).
Broke apart script test globs.
Added option to MiddlewareSpec.
Commit messages
Package name: newrelic
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs