Update dependency newrelic to v7.5.2 #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/newrelic-7.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.0.2->7.5.2Release Notes
newrelic/node-newrelic (newrelic)
v7.5.2Compare Source
v7.5.1Compare Source
Fixed loading config from the main module's directory. Thank you @alexpls for the contribution.
Moved all integration tests that required secrets to the smoke folder.
Fixed LASP/CSP tests so they don't skip on runs where secrets are available.
Modified self-signed SSL cert to use 'localhost' instead of 'ssl.lvh.me' for SSL testing.
Removed unnecessary trace observer configuration validation for host and port.
v7.5.0Compare Source
Added default support for config files with a 'cjs' extension (
newrelic.cjs) in addition tonewrelic.js.Thank you to @Maddemacher for the contribution!
Added ability to specify a custom config file name with the
NEW_RELIC_CONFIG_FILENAMEenvironment variable.Thank you to @Maddemacher for the contribution!
Fixed issue when using the 'new_promise_tracking' feature flag where segment mapping may not get cleaned up for promises which never resolve but have all references removed (and thus get cleaned up by GC).
Adds segment cleanup on 'destroy' when using 'new_promise_tracking' feature flag in addition to the existing 'promiseResolve' hook. Unfortunately, preventing leaks for this edge-case does come with additional overhead due to adding another hook. Memory gains from feature flag usage should still be worth the trade-off and reduced garbage collection may offset perf/CPU impacts or event still result in net gain, depending on the application.
Bumped
@newrelic/test-utilitiesto ^5.1.0.Replaced deprecated
util.isArraywithArray.isArray.Removed unused
listenerCountmethod onShim.Properly bootstraped husky as a
preparescript.Removed commented-out console log from fastify instrumentation.
v7.4.0Compare Source
Updated third party notices and manifest for husky and lint-staged.
Updated redis versioned tests to use unique DB indexes per file to avoid collisions and flushing of in-progress tests.
Pinned hapi 17 versioned tests to only minor/patch versions within 17.x.
Bumped timeout for redis versioned tests.
Wired up husky + lint staged to execute linting on all changed files in pre-commit hook.
Handled a proxy misconfiguration of collector and log an actionable warning message.
Added
flaky_codeandsuccess_delay_mshandling of flaky grpc connections to infinite tracing.Added resources to README to highlight external modules that customers should be aware of and possibly use for their applications.
Logged all New Relic metadata env vars at startup.
Fixed images for improved reader experience.
Thank you to @henryjw for the contribution.
v7.3.1Compare Source
Fixed issue with 'new_promise_tracking' feature flag functionality where segments for ended transactions would get propagated in certain cases by promises that had no continuations scheduled (via await or manually).
If you are experiencing high overhead levels with your promise usage and the agent attached, we recommend testing your application with 'new_promise_tracking' set to true to see if overhead is reduced. You'll also want to verify your data is still being captured correctly in case it falls into a known or unknown limitation of this approach. NOTE: chaining of promise continuations onto an already resolved promise across an async hop (scheduled timer) will result in state-loss with this new functionality turned on. This is a less-common use-case but worth considering with your applications.
Deprecation Warning: The certificate bundle automatically included by New Relic when using the 'certificates' configuration (commonly with proxies) will be disabled by default in the next major version. This is currently targeted for sometime in May. The bundle will be fully removed in later major versions. We recommend testing with the 'certificate_bundle' feature flag set to
falseto determine if you will need to modify your environment or setup your own appropriate bundle. Example configuration:feature_flag: { certificate_bundle: false }.v7.3.0Compare Source
Added new feature-flag 'new_promise_tracking' which enables cleaning up of segment references on native promise resolve instead of destroy. Includes usage of async-await. This can be enabled via
feature_flag: { new_promise_tracking: true }in the config file orNEW_RELIC_FEATURE_FLAG_NEW_PROMISE_TRACKING=1in your ENV vars.Applications with heavy promise usage or high-throughput applications with some promise usage should see moderate to high reduction in memory usage and may see a slight reduction in CPU usage. A bump in throughput may also be noticed in some cases. Results will vary by application.
If you are experiencing high overhead levels with your promise usage and the agent attached, we recommend testing your application with 'new_promise_tracking' set to true to see if overhead is reduced. You'll also want to verify your data is still being captured correctly in case it falls into a known or unknown limitation of this approach. NOTE: chaining of promise continuations onto an already resolved promise across an async hop (scheduled timer) will result in state-loss with this new functionality turned on. This is a less-common use-case but worth considering with your applications.
Fixed memory leak introduced when Infinite Tracing is enabled.
When Infinite Tracing endpoints reconnected they would instantiate a new gRPC client prior to calling
client.recordSpan(). It appears several objects created by grpc-js (ChannelImplementationand child objects, promises, etc.) are held in memory indefinitely due to scheduled timers even when the client is no-longer referenced and the associated stream closed. We now avoid this situation by only creating the client once and then reusing it to establish new stream connections.v7.2.1Compare Source
Dev-only sub-dependency bump of 'y18n' to clear npm audit warnings.
Bumped @grpc/grpc-js to ^1.2.11.
Bumped @grpc/proto-loader to ^0.5.6.
Agent no longer propagates segments for promises via async-hooks when the transaction associated with the parentSegment has ended.
This change reduces the amount of context tracking work needed for certain rare edge-case scenarios involving promises.
Fixed issue where capturing axios request errors could result in a memory leak.
The agent now clears error references on transaction end, which are not used for later processing. Errors returned from 'axios' requests contain a reference to the request object which deeper down has a handle to a promise in
handleRequestError. The TraceSegment associated with that promise has a handle to the transaction, which through the error capture ultimately kept the promise in memory and prevented it from being destroyed to free-up the TraceSegment from the segment map. This change also has the benefit of freeing up some memory early for transactions held onto for transaction traces.Added active transaction check to
wrappedResEndto prevent unecessary work for ended transactions in the case of multipleResponse.prototype.end()invocations.v7.2.0Compare Source
Added feature flag to allow disabling of certificate bundle usage.
Deprecation Warning: The certificate bundle included by New Relic will be disabled by default and then fully removed in later major versions. We recommend testing with the certificate_bundle feature flag set to
falseto determine if you will need to modify your environment or setup your own appropriate bundle. Example configuration:feature_flag: { certificate_bundle: false }.The
NEW_RELIC_NO_CONFIG_FILEenvironment variable is no longer needed to run the agent without a configuration file.Fixed bug where applications with multiple names on a dynamically named host (UUID like) would have instances consolidated, losing per-host breakdowns.
Removed 'host' from agent 'identifier' override to prevent server safety mechanism from kicking in. Host will still be used to identify unique agent instances, so was unnecessary to include as part of the identifier. This also resulted in additional processing overhead on the back-end. The identifier override is still kept in place with multiple application names to continue to allow uniquely identifying instances on the same host with multiple application names where the first name may be identical. For example
app_name['myName', 'unique1']andapp_name['myName', 'unique2']. These names would consolidate down into a single instance on the same host without the identifier override.Fixed bug where truncated http (external) or datastore segments would generate generic spans instead of appropriate http or datastore spans.
Set distributed tracing to enabled in the
newrelic.jstemplate configuration file supplied with the agent.Added module root to shim.require() logging to aid debugging.
Migrated from .npmignore to 'files' list in package.json to control which files are packaged.
Thank you to @JamesPeiris for the initial nudge via PR to move in this direction.
Converted remaining collector unit tests to use tap API.
Added linting to scripts in /bin folder.
Linting rules added are slightly more permissive than production rules and allow full ecma 8.
Added new developer documentation to /docs folder.
This information is ported over from private GHE wiki used prior to going open source. S/O @astorm for original versions of the function wrapping and module instrumentation docs.
v7.1.3Compare Source
Bumped @grpc/grpc-js to ^1.2.7.
Removed index-bad-config test which tested a no-longer possible use-case.
Removed license-key test logic from serverless-harvest test.
Serverless mode does not require a license key as data transfer is handled by the integration.
Added support metric to be able to track usage of cert bundle via usage of custom certificates.
Removed requirement to configure application name when running in AWS Lambda (serverless mode).
Application name is not currently leveraged by New Relic for Lambda invocations. The agent now defaults the application name in serverless mode to remove the requirement of end-user configuration while handling cases if it were to be leveraged in the future.
Stopped binding/propagating segments via
setImmediatefor ended transactions.Fixed bug where agent would attempt to call the 'preconnect' endpoint on the redirect host returned by the previous 'preconnect' call when reconnecting to the New Relic servers.
The 'preconnect' calls will now always use the original agent configuration value. Subsequent endpoints (connect, harvest endpoints, etc.) will continue to leverage the new redirect host value returned by 'preconnect.' The original config values are no-longer overridden.
Fixed issue where a call to
transaction.acceptDistributedTraceHeaderswould throw an error when theheadersparameter is a string.Improved clarity of logging between 'no log file' or disabled agent startup issues.
Removed aws-sdk versioned test filtering.
Removed unused Travis CI scripts.
v7.1.2Compare Source
Fixed bug where the agent failed to reconnect to Infinite Tracing gRPC streams on Status OK at higher log levels.
Removed initial harvest send() call on streaming span event aggregator to prevent warning in logs.
Bumped @newrelic/aws-sdk to ^3.1.0.
v7.1.1Compare Source
Upgrade @grpc/grpc-js to v1.2.5 to fix non-propagation of internal http2 errors
Now allows minor and patch auto-updates.
Added workflow for publishing to npm when a v* tag is pushed to the repo.
Fixes resolveMx test by using example.com for a valid exchange.
v7.1.0Compare Source
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 becomes conflicted, 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 Renovate Bot.
7b1c86aeccto578834a365578834a365to5bfc6ce7175bfc6ce717tob89b9c9b37b89b9c9b37toceac305401⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: yarn.lock
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.