newrelic 7.1.3 → 7.3.1

package/lib/instrumentation/core/http.js

@@ -267,6 +267,11 @@ function wrapResponseEnd(agent, proto) {
         return end.apply(this, arguments)
       }
 
+      if (!txInfo.transaction.isActive()) {
+        logger.trace('wrappedResEnd invoked for ended transaction implying multiple invocations.')
+        return end.apply(this, arguments)
+      }
+
       // If an error happened, add it to the aggregator.
       if (txInfo.error) {
         if (!txInfo.errorHandled || urltils.isError(agent.config, this.statusCode)) {

package/lib/shim/shim.js

@@ -1895,7 +1895,12 @@ function shimRequire(filePath) {
   try {
     return require(path.resolve(this._moduleRoot, filePath))
   } catch (e) {
-    this.logger.debug('Failed to load %j: %s', filePath, e.stack)
+    this.logger.debug(
+      'Failed to load \'%s\' from module root: \'%s\'. Stack: %s',
+      filePath,
+      this._moduleRoot,
+      e.stack
+    )
     return null
   }
 }

package/lib/spans/create-span-event-aggregator.js

@@ -72,6 +72,7 @@ function createStandardAggregator(config, collector, metrics) {
 }
 
 function validateInfiniteTracing(trace_observer) {
+  // TODO: Remove semver check when Node 10 support dropped.
   if (!psemver.satisfies('>=10.10.0')) {
     logger.warn(
       'Infinite tracing disabled: this version of Node is not supported (must be >=10.10.0)'

package/lib/spans/span-event.js

@@ -9,7 +9,7 @@ const Config = require('../config')
 const {truncate} = require('../util/byte-limit')
 
 const {DESTINATIONS} = require('../config/attribute-filter')
-const NAMES = require('../metrics/names')
+
 const HTTP_LIBRARY = 'http'
 const CLIENT_KIND = 'client'
 const CATEGORIES = {
@@ -18,6 +18,9 @@ const CATEGORIES = {
   GENERIC: 'generic'
 }
 
+const EXTERNAL_REGEX = /^(?:Truncated\/)?External\//
+const DATASTORE_REGEX = /^(?:Truncated\/)?Datastore\//
+
 const EMPTY_USER_ATTRS = Object.freeze(Object.create(null))
 
 /**
@@ -200,7 +203,7 @@ class HttpSpanEvent extends SpanEvent {
   }
 
   static testSegment(segment) {
-    return segment.name.startsWith(NAMES.EXTERNAL.PREFIX)
+    return EXTERNAL_REGEX.test(segment.name)
   }
 }
 
@@ -259,7 +262,7 @@ class DatastoreSpanEvent extends SpanEvent {
   }
 
   static testSegment(segment) {
-    return segment.name.startsWith(NAMES.DB.PREFIX)
+    return DATASTORE_REGEX.test(segment.name)
   }
 }
 

package/lib/spans/streaming-span-event.js

@@ -10,7 +10,7 @@ const {truncate} = require('../util/byte-limit')
 const Config = require('../config')
 
 const {DESTINATIONS} = require('../config/attribute-filter')
-const NAMES = require('../metrics/names')
+
 const HTTP_LIBRARY = 'http'
 const CLIENT_KIND = 'client'
 const CATEGORIES = {
@@ -19,6 +19,9 @@ const CATEGORIES = {
   GENERIC: 'generic'
 }
 
+const EXTERNAL_REGEX = /^(?:Truncated\/)?External\//
+const DATASTORE_REGEX = /^(?:Truncated\/)?Datastore\//
+
 /**
  * Specialized span event class for use with infinite streaming.
  * Currently designed to be sent over grpc via the v1.proto definition.
@@ -200,7 +203,7 @@ class StreamingHttpSpanEvent extends StreamingSpanEvent {
   }
 
   static isHttpSegment(segment) {
-    return segment.name.startsWith(NAMES.EXTERNAL.PREFIX)
+    return EXTERNAL_REGEX.test(segment.name)
   }
 }
 
@@ -269,7 +272,7 @@ class StreamingDatastoreSpanEvent extends StreamingSpanEvent {
   }
 
   static isDatastoreSegment(segment) {
-    return segment.name.startsWith(NAMES.DB.PREFIX)
+    return DATASTORE_REGEX.test(segment.name)
   }
 }
 

package/lib/transaction/index.js

@@ -225,9 +225,28 @@ Transaction.prototype.end = function end() {
   }
 
   this.agent.emit('transactionFinished', this)
+
+  // Do after emit so all post-processing can complete
+  this._cleanUneededReferences()
+
   return this
 }
 
+/**
+ * Cleans up references that will not be used later for processing such as
+ * transaction traces.
+ *
+ * Errors won't be needed for later processing but can contain extra details we
+ * don't want to hold in memory. Particularly, axios errors can result in indirect
+ * references to promises which will prevent them from being destroyed and result
+ * in a memory leak. This is due to the TraceSegment not getting removed from the
+ * async-hooks segmentMap because 'destroy' never fires.
+ */
+Transaction.prototype._cleanUneededReferences = function _cleanUneededReferences() {
+  this.userErrors = null
+  this.exceptions = null
+}
+
 /**
  * For web transactions, this represents the time from when the request was received
  * to when response was sent.  For background transactions, it is equal to duration
@@ -768,6 +787,11 @@ function _linkExceptionToSegment(exception) {
 Transaction.prototype.addException = _addException
 
 function _addException(exception) {
+  if (!this.isActive()) {
+    logger.trace('Transaction is not active. Not capturing error: ', exception)
+    return
+  }
+
   this._linkExceptionToSegment(exception)
   this.exceptions.push(exception)
 }
@@ -782,6 +806,11 @@ function _addException(exception) {
 Transaction.prototype.addUserError = _addUserError
 
 function _addUserError(exception) {
+  if (!this.isActive()) {
+    logger.trace('Transaction is not active. Not capturing user error: ', exception)
+    return
+  }
+
   this._linkExceptionToSegment(exception)
   this.userErrors.push(exception)
 }

package/newrelic.js

@@ -28,7 +28,7 @@ exports.config = {
      *
      * @env NEW_RELIC_DISTRIBUTED_TRACING_ENABLED
      */
-    enabled: false
+    enabled: true
   },
   logging: {
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "newrelic",
-  "version": "7.1.3",
+  "version": "7.3.1",
   "author": "New Relic Node.js agent team <nodejs@newrelic.com>",
   "license": "Apache-2.0",
   "contributors": [
@@ -125,7 +125,7 @@
     "docs": "npm ci && jsdoc -c ./jsdoc-conf.json --private -r .",
     "integration": "npm run prepare-test && npm run sub-install && time tap --no-esm test/integration/**/**/*.tap.js --timeout=180 --no-coverage",
     "prepare-test": "npm ci && npm run ca-gen && npm run ssl && npm run docker-env",
-    "lint": "eslint ./*.js lib test",
+    "lint": "eslint ./*.js lib test bin",
     "public-docs": "npm ci && jsdoc -c ./jsdoc-conf.json --tutorials examples/shim api.js lib/shim/ lib/transaction/handle.js && cp examples/shim/*.png out/",
     "publish-docs": "./bin/publish-docs.sh",
     "services": "./bin/docker-services.sh",
@@ -143,8 +143,8 @@
     "newrelic-naming-rules": "./bin/test-naming-rules.js"
   },
   "dependencies": {
-    "@grpc/grpc-js": "^1.2.7",
-    "@grpc/proto-loader": "^0.5.5",
+    "@grpc/grpc-js": "^1.2.11",
+    "@grpc/proto-loader": "^0.5.6",
     "@newrelic/aws-sdk": "^3.1.0",
     "@newrelic/koa": "^5.0.0",
     "@newrelic/superagent": "^4.0.0",
@@ -171,7 +171,7 @@
     "commander": "^7.0.0",
     "eslint": "^6.8.0",
     "express": "*",
-    "fastify": "^2.14.1",
+    "fastify": "^2.15.3",
     "generic-pool": "^3.6.1",
     "glob": "^7.1.2",
     "got": "^8.0.1",
@@ -198,5 +198,18 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/newrelic/node-newrelic.git"
-  }
+  },
+  "files": [
+    "index.js",
+    "api.js",
+    "stub_api.js",
+    "newrelic.js",
+    "README.md",
+    "LICENSE",
+    "NEWS.md",
+    "THIRD_PARTY_NOTICES.md",
+    "lib/",
+    "bin/tracetractor",
+    "bin/test-naming-rules.js"
+  ]
 }

package/CONTRIBUTING.md

@@ -1,135 +0,0 @@
-# Guidelines for Contributing Code
-
-New Relic welcomes code contributions by the Node community to this module, and
-have taken effort to make this process easy for both contributors and our
-development team.
-
-## Process
-
-### Feature Requests
-
-Feature requests should be submitted in the [Issue tracker](../../issues), with
-a description of the expected behavior & use case. Before submitting an Issue,
-please search for similar ones in the [closed
-issues](../../issues?q=is%3Aissue+is%3Aclosed+label%3Aenhancement).
-
-### Pull Requests
-
-We can only accept PRs for version v6.11.0 or greater due to open source
-licensing restrictions.
-
-### Code of Conduct
-
-Before contributing please read the [code of conduct](https://github.com/newrelic/.github/blob/main/CODE_OF_CONDUCT.md)
-
-Note that our [code of conduct](https://github.com/newrelic/.github/blob/main/CODE_OF_CONDUCT.md) applies to all platforms
-and venues related to this project; please follow it in all your interactions
-with the project and its participants.
-
-### Contributor License Agreement
-
-Keep in mind that when you submit your Pull Request, you'll need to sign the
-CLA via the click-through using CLA-Assistant. If you'd like to execute our
-corporate CLA, or if you have any questions, please drop us an email at
-opensource@newrelic.com.
-
-For more information about CLAs, please check out Alex Russell’s excellent
-post, [“Why Do I Need to Sign
-This?”](https://infrequently.org/2008/06/why-do-i-need-to-sign-this/).
-
-### Slack
-
-We host a public Slack with a dedicated channel for contributors and
-maintainers of open source projects hosted by New Relic. If you are
-contributing to this project, you're welcome to request access to the
-\#oss-contributors channel in the newrelicusers.slack.com workspace. To request
-access, see https://newrelicusers-signup.herokuapp.com/.
-
-## PR Guidelines
-
-### Version Support
-
-When contributing, keep in mind that New Relic customers (that's you!) are running many different versions of Node, some of them pretty old. Changes that depend on the newest version of Node will probably be rejected, especially if they replace something backwards compatible.
-
-Be aware that the instrumentation needs to work with a wide range of versions of the instrumented modules, and that code that looks nonsensical or overcomplicated may be that way for compatibility-related reasons. Read all the comments and check the related tests before deciding whether existing code is incorrect.
-
-If you’re planning on contributing a new feature or an otherwise complex contribution, we kindly ask you to start a conversation with the maintainer team by opening up an Github issue first.
-
-### General Guidelines
-
-In general, we try to limit adding third-party production dependencies. If one is necessary, please be prepared to make a clear case for the need.
-
-### Coding Style Guidelines/Conventions
-
-We use eslint to enforce certain coding standards. Please see our [.eslintrc](./.eslintrc.js) file for specific rule configuration.
-
-### Testing Guidelines
-
-The agent includes a suite of unit and functional tests which should be used to
-verify your changes don't break existing functionality.
-
-Unit tests are stored in `test/`. They're written in
-[node-tap](https://github.com/isaacs/node-tap), and have the extension `.test.js`.
-
-Generic functional tests are stored in `test/integration/`. They're written in
-[node-tap](https://github.com/isaacs/node-tap), and have the extension
-`.tap.js`.
-
-Functional tests against specific versions of instrumented modules are stored
-in `test/versioned/`. They are also written in `node-tap`.
-
-#### Setup
-
-To run the tests you need an openssl command-line binary, and some services:
-
-* Cassandra
-* Memcached
-* MongoDB
-* MySQL
-* Postgres
-* Redis
-
-If you have these all running locally on the standard ports, then you are good
-to go. However, the suggested path is to use [Docker](http://www.docker.com).
-If you use macOS or Windows, install [Docker Desktop]
-(https://www.docker.com/products/docker-desktop). Then, run `npm run services`
-to download and launch docker containers for each of the above services.
-
-If you have these services available on non-standard ports or elsewhere on your
-network, you can use the following environment variables to tell the tests
-where they are:
-
-* NR_NODE\_TEST_<service>\_HOST
-* NR_NODE\_TEST_<service>\_PORT
-
-The service token is the all-caps version of the service name listed above.
-
-#### Running Tests
-
-Running the test suite is simple. Just run:
-
-    npm test
-
-This will install all the necessary modules (and do any required SSL
-certificate creation) and run the unit tests in standalone mode, followed by
-the functional tests if all of the unit tests pass.
-
-If you don't feel like dealing with the hassle of setting up the servers, just
-the unit tests can be run with:
-
-    npm run unit
-
-#### Writing Tests
-
-For most contributions it is strongly recommended to add additional tests which
-exercise your changes. This helps us efficiently incorporate your changes into
-our mainline codebase and provides a safeguard that your change won't be broken
-by future development. Because of this, we require that all changes come with
-tests. You are welcome to submit pull requests with untested changes, but they
-won't be merged until you or the development team have an opportunity to write
-tests for them.
-
-There are some rare cases where code changes do not result in changed
-functionality (e.g. a performance optimization) and new tests are not required.
-In general, including tests with your pull request dramatically increases the
-chances it will be accepted.

package/Migration Guide.md

@@ -1,271 +0,0 @@
-
-# Migration Guide
-This guide is intended to help with upgrading major versions of the Node Agent.
-This information can also be found on [our documentation website][upgrade-doc].
-
-## Upgrading to Agent v5
-
-### Breaking Changes
-
-**Removed deprecated API methods**: The following API methods had been marked as
-deprecated since agent v2, and have now been fully removed from the codebase:
-
-* `newrelic.addCustomParameter()`
-
-  Replace with `newrelic.addCustomAttribute()`.
-
-* `newrelic.addCustomParameters()`
-
-  Replace with `newrelic.addCustomAttributes()`.
-
-* `newrelic.createWebTransaction()`
-
-  Replace with `newrelic.startWebTransaction()` and `newrelic.getTransaction()`.
-
-* `newrelic.createBackgroundTransaction()`
-
-  Replace with `newrelic.startBackgroundTransaction()` and `newrelic.getTransaction()`.
-
-* `newrelic.createTracer()`
-
-  Replace with `newrelic.startSegment()`.
-
-**Removed `ignore_server_configuration` setting**: This setting was only implemented
-by the Node agent, so removing it improves parity with other language agents.
-
-**Removed `node-cassandra-cql` instrumentation**: This [library][node-cassandra-cql]
-has not been updated in 5 years, and has since been superseded by
-[cassandra-driver](https://www.npmjs.com/package/cassandra-driver), which is
-supported by the agent.
-
-**Removed deprecated configuration settings**: The following configuration
-settings have been deprecated since agent v3, and have now been removed from the
-codebase:
-
-* `capture_params`
-
-  Replaced with `attributes.enabled`. By default, request attributes are not
-  sent to New Relic. Set `attributes.enabled: true` to include agent-defined or
-  custom attributes in traces.
-
-* `ignored_params`
-
-  Replaced with `attributes.exclude`. Add any request attribute keys to the
-  `attributes.exclude` list. Now, instead of having to be an exact match,
-  wildcards (`*`) may be appended to each item for broader filtering.
-
-**Updated custom metric naming**: Custom metrics are now prefixed with `Custom/`.
-Existing insights queries may need to be addressed moving forward.
-
-### Node Version Support
-
-The agent now only supports Node version 6 and above, which brings it up to date
-with Node's [LTS][node-lts-schedule] schedule. Customers running Node 4.x or 5.x
-will need to upgrade to a supported version of Node or remain on the v4 agent.
-
-### Released Feature Flags
-* `custom_instrumentation`: This feature is no longer configurable.
-* `custom_metrics`: This feature is no longer configurable.
-* `synthetics`: This feature is no longer configurable.
-* `native_metrics`: This feature is now controlled by the
-  `plugins.native_metrics.enabled` configuration value.
-
---------------------------------------------------------------------------------
-
-## Upgrading to Agent v4
-
-### Breaking Changes
-
-**Upgraded https-proxy-agent from v0 to v2**: This dependency has been updated
-due to a security issue in the version of `https-proxy-agent` the New Relic Node.js
-agent used. `https-proxy` v2 is incompatible with node v0.10 and v0.12,
-requiring deprecation of those versions for the agent. There is no required
-action to migrate from v3 to v4 of New Relic's Node.js agent.
-
-### Node Version Support
-The earliest version of Node supported by the v4 agent is 4. Node 0.10 and 0.12,
-which have not been updated since February of 2017, are not supported by v4.
-Customers running Node 0.10 or 0.12 will need to upgrade to a supported version
-of Node or remain on the v3 agent.
-
-[Node 4 is also no longer receiving updates][node-lts-schedule], but we will
-continue to support this version of Node for the time being. We highly recommend
-moving to a newer version of Node as soon as possible. The next major version of
-the New Relic Node Agent will likely remove support for it.
-
---------------------------------------------------------------------------------
-
-## Upgrading to Agent v3
-
-### Breaking Changes
-
-**Removed SSL configuration**: The agent will always connect to New Relic
-servers using TLS to encrypt communications. The `ssl` configuration value and
-`NEW_RELIC_USE_SSL` environment value are ignored. If set to any value other
-than `true`, a warning is logged and the value is ignored.
-
-**Request parameters now prefixed with `request.parameters.`**: Any request
-parameters, such as route (`/user/:userId`) or query (`/user?userId=123`)
-parameters will now be prefixed with `request.parameters.` when collected. For
-example, the route parameter from `/user/:userId` would be collected as
-`request.parameters.userId`.
-
-Any Insights dashboards, Alerts, or other NRQL queries using these attributes
-must be updated to look for the new attributes instead.
-
-### Released Feature Flags
-
-* `send_request_uri_attribute`: This feature is no longer configurable.
-
---------------------------------------------------------------------------------
-
-## Upgrading to Agent v2
-
-### Breaking Changes
-
-**Reversed naming and ignore rules**: Previously, rules defined in the config
-properties `rules.name` and `rules.ignore` were applied in reverse order, the
-first rule in the list was applied last. Agent v2 now applies rules in the
-order they are defined, so the first rule in the list is applied first.
-
-Users of naming rules in the v1 agent will need to reverse the order of their
-rules in the configuration if they're noticing any issues.
-
-**De-duplicated HTTP request transactions**: The v1 agent starts a new
-transaction for each _listener_ on an HTTP server's `request` event. In
-applications with multiple listeners on the `request` event this would result
-in extraneous transactions being created that almost always did not get named
-correctly. In v2 the agent only creates a single transaction for each `request`
-event emitted.
-
-Any users who utilized multiple `request` event listeners and added a call to
-`newrelic.ignoreTransaction()` to remove the extra transactions should remove
-those calls.
-
-**Stopped swallowing outbound request errors**: In v1 the Node Agent swallows
-unhandled `error` events emitted by outbound HTTP request objects. Agent v2
-removed this behavior in favor of not changing normal Node execution, meaning
-the `error` event will always be emitted.
-
-If you are making outbound requests and currently do not listen for the `error`
-event, add a listener and handle the error as appropriate for your application.
-
-### Updated configuration options
-
-In `newrelic.js`, edit the configuration properties you use for compatibility
-with the latest versions:
-
-* `capture_params`
-
-  Replaced with `attributes.enabled`. By default, request attributes are not
-  sent to New Relic. Set `attributes.enabled`: true to include agent-defined or
-  custom attributes in traces.
-
-* `ignored_params`
-
-  Replaced with `attributes.exclude`. Add any request attribute keys to the
-  `attributes.exclude` list. Now, instead of having to be an exact match,
-  wildcards (`*`) may be appended to each item for broader filtering.
-
-**NOTE**: The new properties also have overrides for specific destinations
-(`transaction_tracer`, `transaction_events`, `error_collector`, and
-`browser_monitoring`). For example, setting
-`transaction_tracer.attributes.enabled: false`, would restrict attributes from
-being collected in transaction traces, while still allowing them for all others,
-assuming the root `attributes.enabled` is `true`. Please see
-[Node.js agent configuration](https://docs.newrelic.com/docs/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration)
-for more details.
-
-### Deprecated API Methods
-These methods have been marked as deprecated in Agent v2 and will be removed in
-v3.
-
-* `newrelic.createWebTransaction()`
-
-  Replace with `newrelic.startWebTransaction()` and `newrelic.getTransaction()`.
-
-* `newrelic.createBackgroundTransaction()`
-
-  Replace with `newrelic.startBackgroundTransaction()` and `newrelic.getTransaction()`.
-
-* `newrelic.addCustomParameter()`
-
-  Replace with `newrelic.addCustomAttribute()`.
-
-* `newrelic.addCustomParameters()`
-
-  Replace with `newrelic.addCustomAttributes()`.
-
-### New API Methods
-
-* [`newrelic.getTransaction()`](https://newrelic.github.io/node-newrelic/docs/API.html#getTransaction)
-
-  This method gets a reference to the currently running transaction. It should
-  be used in conjunction with `newrelic.startWebTransaction`,
-  `newrelic.startBackgroundTransaction`, or with callback-based message
-  consumer services. See our [Trouble Shooting][messaging-troubleshooting-doc]
-  documentation for more information on its usage.
-
-* [`newrelic.startWebTransaction()`](https://newrelic.github.io/node-newrelic/docs/API.html#startWebTransaction)
-  [`newrelic.startBackgroundTransaction()`](https://newrelic.github.io/node-newrelic/docs/API.html#startBackgroundTransaction)
-
-  These new API methods replace the older `create*Transaction` methods. They
-  are easier to use and seamlessly work with promises. Note that unlike the old
-  method, the provided callback is invoked immediately.
-
-* [`newrelic.instrument()`](https://newrelic.github.io/node-newrelic/docs/API.html#instrument)
-  [`newrelic.instrumentDatastore()`](https://newrelic.github.io/node-newrelic/docs/API.html#instrumentDatastore)
-  [`newrelic.instrumentWebframework()`](https://newrelic.github.io/node-newrelic/docs/API.html#instrumentWebframework)
-  [`newrelic.instrumentMessages()`](https://newrelic.github.io/node-newrelic/docs/API.html#instrumentMessages)
-
-  These methods can be used to add custom instrumentation for 3rd party modules,
-  including those already instrumented by the Node Agent. See our
-  [instrumentation tutorials][instrumentation-tutorial] for more information
-  on using these methods.
-
-* `newrelic.addCustomAttribute()`
-
-  Use this method to add a custom trace attribute.
-
-* `newrelic.addCustomAttributes()`
-
-  Use this method to add multiple custom trace attributes.
-
-### Node Version Support
-The earliest version of Node supported by the v2 agent is 0.10. Node 0.8, which
-has not been updated since July of 2014, is not supported by v2. Customers
-running Node 0.8 will need to upgrade to a supported version of Node or remain
-on the v1 agent. [Node 0.10 is also no longer receiving updates][node-lts-schedule],
-but we will continue to support this version of Node for the time being. We
-highly recommend moving to a newer version of Node as soon as possible. The
-next major version of the New Relic Node Agent will likely remove support for
-it.
-
-### npm Version Support
-The agent now requires npm version 2.0.0 or higher. This version of npm comes
-packaged with Node 0.10.44 or higher. If you are using an earlier version of
-Node 0.10 you will need to first install npm 2.0.0 or higher or upgrade to a
-newer version of Node. Version 2 of npm can be installed with:
-
-```sh
-$ npm install --global npm@2
-```
-
-### Released Feature Flags
-* `express_segments`: This feature is no longer configurable.
-* `cat`: This feature is now controlled by the `cross_application_tracer.enabled`
-  configuration value.
-
-### New Framework Minimum Versions
-
-| Module  | Old Minimum | New Minimum |
-|---------|-------------|-------------|
-| express | 2.0.0 | 4.6.0 |
-| mysql   | 0.9.0 | 2.0.0 |
-
-
-[upgrade-doc]: https://docs.newrelic.com/docs/agents/nodejs-agent/installation-configuration/upgrade-node-agent-versions
-[messaging-troubleshooting-doc]: https://docs.newrelic.com/docs/agents/nodejs-agent/troubleshooting/troubleshoot-message-consumers
-[instrumentation-tutorial]: https://newrelic.github.io/node-newrelic/docs/tutorial-Instrumentation-Basics.html
-[node-lts-schedule]: https://github.com/nodejs/LTS/tree/2b4253#lts-schedule1
-[node-cassandra-cql]: https://www.npmjs.com/package/node-cassandra-cql

package/ROADMAP_Node.md

@@ -1,24 +0,0 @@
-# Node Agent Roadmap
-
-## Product Vision
-The goal of the Node agent is to provide complete visibility into the health of your service. The agent provides metrics about the runtime health of your service and the process it runs in, and traces that show how specific requests are performing. It also provides information about the environment in which it is running, so you can identify issues with specific hosts, regions, deployments, and other facets. 
-
-New Relic is moving toward OpenTelemetry. OpenTelemetry is a unified standard for service instrumentation. You will soon see an updated version of the agent that uses the OpenTelemetry SDK and [auto-]instrumentation as its foundation. OpenTelemetry will include a broad set of high-quality community-contributed instrumentation and a powerful vendor-neutral API for adding your own instrumentation.
-
-
-## Roadmap
-### Description
-This roadmap project is broken down into the following sections:
-
-- **Now**:
-    - This section contains features that are currently in progress.
-- **Next**:
-    - This section contains work planned within the next three months. These features may still be deprioritized and moved to Future.
-- **Future**:
-    - This section is for ideas for future work that is aligned with the product vision and possible opportunities for community contribution. It contains a list of features that anyone can implement. No guarantees can be provided on if or when these features will be completed.
-     
-
-**The roadmap project is found [here](https://github.com/orgs/newrelic/projects/11)**
-
-#### Disclaimers
-> This roadmap is subject to change at any time. Future items should not be considered commitments.

package/SECURITY.md

@@ -1,5 +0,0 @@
-# Reporting Security Vulnerabilities
-
-New Relic is committed to the security of our customers and your data. We believe that engaging with security researchers through our coordinated disclosure program is an important means to achieve our security goals.
-
-If you believe you have found a security vulnerability in one of our products or websites, we welcome and greatly appreciate you reporting it to New Relic's coordinated disclosure program.  Please see our [website for more information on how to report a vulnerability](https://docs.newrelic.com/docs/security/new-relic-security/data-privacy/reporting-security-vulnerabilities).