Update dependency newrelic to v9.15.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
newrelic	9.0.2 -> 9.15.0

---

Release Notes

newrelic/node-newrelic (newrelic)

v9.15.0

Compare Source

• Added a new configuration option heroku.use_dyno_names to specify whether or not to use process.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 set heroku.use_dyno_names to false. You can also control this configuration options with the environment variable of NEW_RELIC_HEROKU_USE_DYNO_NAMES. Thanks @​benney-au-le for your contribution 🚀

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.

v9.14.1

Compare Source

• Restored assigning loaded version of agent to require.cache as __NR_cache instead of a symbol to properly detect attempts at loading agent twice.

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.

v9.14.0

Compare Source

• Added new API function called setErrorGroupCallback, which provides a way for you to customize the error.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:

• 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.

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 be enduser.id.

• Added default configuration for security agent.

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.

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:

• 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.

v9.12.0

Compare Source

v9.11.0

Compare Source

v9.11.0 (2023-03-08)

• Added instrumentation for Prisma(@prisma/client).
  • Miniumum supported version of @prisma/client is 4.0.0.
  • Captures spans for queries.
    • It names them based on the model and action.(i.e. Datastore/statement/Prisma/user/create)
    • For statements and queries using the $queryRaw, $executeRaw, $queryRawUnsafe, and $executeRawUnsafe the names will be aligned with the raw SQL.(i.e. Datastore/statement/Prisma/User/select)
  • Captures database metrics for all statements and queries.
  • Captures SQL Traces.
  • Provides connection between application and database server via service maps.

Huge shoutout to @​osmanmrtacar for the original contribution 🙏🏻

• Updated @grpc/protoloader from 0.7.4 to 0.7.5.
• Updated @grpc/grpc-js from 1.8.7 to 1.8.8.

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.

v9.10.2

Compare Source

v9.10.2 (2023-02-21)

• fix: Replaced request.aborted with response.close in HTTP instrumentation.
• Fixed issue where setting NEW_RELIC_GRPC_IGNORE_STATUS_CODES was not properly parsing the codes as integers, thus not ignoring reporting errors of certain status codes.
• Upgraded @grpc/grpc-js from 1.8.4 to 1.8.7.

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.

v9.10.1

Compare Source

• Fixed error with Lambda/ALB serverless instrumentation when no response headers were included

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.

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:

• 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.

v9.9.0

Compare Source

v9.9.0 (2023-02-06)

• Added support for url obfuscation using regex (Thanks for your contribution @​matewilk)

  • For Distributed Tracing, this means that:
    • Incoming and outgoing requests' path will be obfuscated
    • Transaction's request.url attribute will be obfuscated
    • Span's http.uri path will be obfuscated
  • For transactions, this means that:
    • Transaction trace details url will be obfuscated
  • With the following example configuration, url obfuscation will turn /api/v1/users/12345456/edit to /api/v1/users/**/edit.

    url_obfuscation: {
      enabled: true,
      regex: {
        pattern: /(\/api\/v1\/users\/)([\d]+)(\/.*$)/,
        flags: "i",
        replacement: '$1**$3'
      }
    }

  • You can also use environment variables to configure url obfuscation:

    NEW_RELIC_URL_OBFUSCATION_ENABLED: "true",
    NEW_RELIC_URL_OBFUSCATION_REGEX_PATTERN: '/(\/api\/v1\/users\/)([\d]+)(\/.*$)/',
    NEW_RELIC_URL_OBFUSCATION_REGEX_FLAGS: 'i',
    NEW_RELIC_URL_OBFUSCATION_REGEX_REPLACEMENT: '$1**$3'

• Add a new tracking type of instrumentation. This will be responsible for logging Supportability/Features/Instrumentation/OnResolved/<pkg> and Supportability/Features/Instrumentation/OnResolved/<pkg>/Version/<version> metrics when packages are required.

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.

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 like winston.createLogger.

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.

v9.8.0

Compare Source

v9.8.0 (2023-01-17)

• Updated getBrowserTimingHeader to allow Browser Agent to be generated even when not in a Transaction by adding allowTransactionlessInjection to function options. allowTransactionlessInjection is a boolean option, and when set to true, 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 calling getBrowserTimingHeader. To wait until the agent is connected, you can add the following check to your code:

if (!newrelic.agent.collector.isConnected()) {
  await new Promise((resolve) => {
    newrelic.agent.on('connected', resolve)
  })
}

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.

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:

• 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.

v9.7.4

Compare Source

• Fixed system info gathering to prevent unhandled promise rejection when an error occurs reading /proc information.

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.

v9.7.3

Compare Source

v9.7.3 (2022-12-12)

• Added support for Code Level Metrics on API methods: startSegment, startBackgroundTransaction, and startWebTransaction.

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.

v9.7.2

Compare Source

• 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.

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

  • 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.

v9.7.0

Compare Source

• 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.

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.

  • 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 be NEW_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:

• 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.

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:

• 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.

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

newrelic.recordLogEvent({ message: 'hello world', level: 'info' })`

Note: If you are including a serialized error make sure it is 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.

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.

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:

• 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.

v9.2.0

Compare Source

v9.2.0 (2022-10-06)

• Added ability to instrument ES Modules with the New Relic ESM Loader.

  • Example ESM application

• 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 except newrelic.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> when max_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.

v9.1.0

Compare Source

• 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.

• Enhanced supportability metrics for ESM support.

  • Added new metrics to track usage of ESM loader(Supportability/Features/ESM/Loader and Supportability/Features/ESM/UnsupportedLoader).
  • Updated instrumentation map to include an optional "friendly name" for tracking metrics.

• Enabled re-throwing ESM import errors of newrelic.js so that the user is informed to rename it to newrelic.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.

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:

• 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.

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.