newrelic 7.1.2 → 7.3.0

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

package/THIRD_PARTY_NOTICES_ADDENDUM.md

@@ -1,213 +0,0 @@
-# Third Party License Addendum
-
-Developers Note:  The following license could not be autogenerated by the New Relic OSS cli tool and needs to be manually copied to the `THIRD_PARTY_LICENSE.md` after running the tool.
-
-## Footer
-
-Portions copyright Node.js contributors. Depending on your existing libraries and package management settings,
-your systems may call externally maintained libraries in addition to those listed above.
-See [here](https://nodejs.org/en/docs/meta/topics/dependencies/) and [here](https://github.com/nodejs/node/blob/v4.3.1/LICENSE)
-for additional details regarding externally maintained libraries and certain related licenses and notices.”
-
-## ADDITIONAL LICENSE(S)
-
----
-
-<!-- licence -->
-### Symantec
-
-This product includes certificates from Symantec which are used under the
-following license (https://docs.broadcom.com/doc/root-certificate-license-agreement-en):
-
-```
-ROOT CERTIFICATE LICENSE AGREEMENT
-SYMANTEC CORPORATION AND/OR ITS AFFILIATES (“SYMANTEC”) IS WILLING TO PROVIDE THE
-ROOT CERTIFICATES TO YOU AS THE INDIVIDUAL, THE COMPANY, OR THE LEGAL ENTITY THAT
-WILL BE UTILIZING THE ROOT CERTIFICATES (REFERENCED BELOW AS “YOU” OR “YOUR”)
-ONLY ON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS OF THIS AGREEMENT
-(“AGREEMENT”). READ THE TERMS AND CONDITIONS OF THIS AGREEMENT CAREFULLY
-BEFORE USING THE ROOT CERTIFICATES. THIS IS A LEGAL AND ENFORCEABLE CONTRACT
-BETWEEN YOU AND SYMANTEC. BY USING THE ROOT CERTIFICATES, YOU AGREE TO THE
-TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS AND
-CONDITIONS, MAKE NO FURTHER USE OF THE ROOT CERTIFICATES. UNLESS OTHERWISE
-DEFINED HEREIN, CAPITALIZED TERMS WILL HAVE THE MEANING GIVEN IN THE “DEFINITIONS”
-SECTION OF THIS AGREEMENT AND SUCH CAPITALIZED TERMS MAY BE USED IN THE
-SINGULAR OR IN THE PLURAL, AS THE CONTEXT REQUIRES.
-
-ROOT CERTIFICATE TERMS AND CONDITIONS
-1. DEFINITIONS.
-"Certificate" means an electronic file that, at least, states a name or identifies the issuing Certificate
-Authority, identifies the subscriber, contains the subscriber's public key, identifies the Certificate's
-operational period, contains a Certificate serial number, and contains a digital signature of the issuing
-Certificate Authority.
-“Certificate Authority” or “CA” means a person or entity authorized to issue, suspend, or revoke
-Certificates.
-“Intermediate CA” means a CA Certificate signed by a Root Certificate Intermediate that issues
-Certificates either to end-entities or other Certificate Authorities, but not to both.
-"Products" means all versions of Your product or service with which the Root Certificates are incorporated
-(including successor products and services or any major or minor upgrades thereto).
-"Root Certificate" means a self-signed Certificate issued by a top-level Certificate Authority to itself, which
-includes such Certificate Authority's public key. The Root Certificates and Root Certificate files to be
-provided by Company to Customer pursuant to this Agreement are available for download at
-https://www.verisign.com/support/roots.html, https://www.thawte.com/roots/index.html or
-https://www.geotrust.com/resources/rootcertificates/index.html.
-2. LICENSE. During the term of this Agreement, Symantec grants You a royalty-free, non-exclusive, nontransferable license to (a) use the Root Certificate for the purposes of testing (without the right to modify);
-(b) make copies of Root Certificates only in order to embed and incorporate them, unmodified and in full,
-as roots in Your Products; (c) distribute the Root Certificates as embedded and incorporated in such
-Products; and (d) use the relevant logos and trademarks of Symantec in Your marketing materials,
-advertisements, product data sheets, product packaging and websites solely conjunction with the
-distribution of the Root Certificates in accordance with Symantec’s published guidelines for such usage.
-You shall not have the right to further distribute the Root Certificates other than as described herein
-without an additional license grant, in a separate writing, from Symantec.
-3. RESTRICTIONS. You may not: (a) modify or create any derivative works of Root Certificates; (b)
-assign, sublicense, sell, rent, or lease Symantec's root keys or Root Certificates; (c) use such Root
-Certificates except as expressly permitted under this Agreement; (d) remove or alter any trademark, logo,
-copyright, or other proprietary notices, legends, symbols, or labels provided in the Root Certificates; or (e)
-certify, or cause a third party to certify, the public key contained in the Root Certificates by issuing or
-creating a Certificate containing such public key.
-4. CUSTOMER’S OBLIGATIONS.
-4.1. During the term of this Agreement, You shall use commercially reasonable efforts regularly check the
-applicable Symantec URL for updates to the Root Certificates and update Root Certificates embedded
-into Your Products with the most currently available Root Certificates, unmodified and in full, or as a patch
-or update. If Symantec updates its Root Certificates,, You shall use commercially reasonable efforts to (i)
-discontinue all copying and use of the Root Certificates which have been replaced, and (ii) to use
-Symantec’s then-current Root Certificates. Any updates to the Root Certificates are incorporated into and
-subject to the terms of this Agreement.
-4.2. You shall appoint at least one (1) individual as the administrative contact designated to address any
-Root Certificate issues and shall provide the contact information for such individual to dl-tssroot@symantec.com.
-4.3 In the event You become aware of or suspect any event that diminishes the integrity of Symantec's
-data or public key system ("Compromise"), You shall immediately notify Symantec at dl-tss-
-root@symantec.com of such Compromise, and take reasonable steps to assist and cooperate with
-Symantec to remedy the Compromise.
-4.4 In the event that Symantec modifies these terms of use for the Root certificates for all end users,
-Symantec shall post the modified terms for the Agreement on the applicable URL and may post the
-modified terms on the Symantec corporate website. You shall be responsible for regularly checking the
-applicable URL for modifications to this Agreement. Such modifications shall be effective and binding on
-Customer within thirty (30) days of Symantec’s posting such modifications to its website. If you do not
-accept the modified Agreement, discontinue use of the Root Certificates and this Agreement will be
-deemed as terminated.
-5. CONFIDENTIALITY.
-5.1. Confidential Information. "Confidential Information" means the root private keys corresponding to the
-public key in a Root Certificate, and any confidential, trade secret, or other proprietary information
-disclosed by a party to the other party under this Agreement, except for Information that: (i) is public
-knowledge at the time of disclosure, (ii) was known by the receiving party before disclosure by the
-disclosing party, or becomes public knowledge or otherwise known to the receiving party after such
-disclosure, other than by breach of a confidentiality obligation, or (iii) is independently developed by the
-receiving party by persons without access to Confidential Information of the disclosing party.
-5.2. Protection of Confidential Information. The receiving party shall: (i) not disclose the Confidential
-information to any third party, (ii) not use the Confidential Information except for purposes of performing
-this Agreement, and (iii) take steps consistent with its protection of its own confidential and proprietary
-information (but in no event exercise less than reasonable care) to prevent unauthorized disclosure of the
-Confidential Information. Each party acknowledges that breach of this Section 5 may cause irreparable
-harm to the disclosing party entitling the disclosing party to injunctive relief, among other remedies.
-5.3. Mutual Cooperation. Each party will notify and cooperate with the other party in enforcing the
-disclosing party's rights if such party becomes aware of a threatened or actual violation of the
-confidentiality requirements of this Section 5. Each party shall have confidentiality agreements with its
-employees, agents or independent contractors sufficient in scope to fulfill its confidentiality obligations
-under this Agreement.
-6. INTELLECTUAL PROPERTY. You acknowledge that Symantec, including its wholly owned
-subsidiaries, retains all intellectual property rights and title (including any patent, copyright, trademark,
-trade secret, and other rights) in and to the Root Certificates, the public and private keys corresponding to
-such Root Certificates ("Symantec Intellectual Property"). This Agreement does not give You any
-intellectual property rights in the Symantec intellectual property except for the license granted in Section
-2. To the extent You use Symantec's trademarks or logos as permitted herein, You agree to comply with
-all usage requirements set forth in the then current version of Symantec's Logo and Trademark Usage
-Guide (http://www.symantec.com/about/profile/policies/trademarks.jsp) and any other guides and
-procedures of Symantec.
-7. NO WARRANTIES. THE ROOT CERTIFICATES, INCLUDING UPDATES, ARE PROVIDED "AS IS"
-WITHOUT ANY WARRANTY WHATSOEVER. SYMANTEC HEREBY DISCLAIMS ALL WARRANTIES,
-WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WITHOUT LIMITATION, ANY
-IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NONINFRINGEMENT OF THIRD PARTY RIGHTS.
-8. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY WILL
-SYMANTEC OR ITS LICENSORS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY
-CONSEQUENTIAL, INDIRECT, SPECIAL, INCIDENTAL, OR EXEMPLARY DAMAGES, WHETHER
-FORESEEABLE OR UNFORESEEABLE, EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES. YOU WILL TAKE REASONABLE MEASURES TO INSURE THAT
-THE TERMS AND CONDITIONS SET FORTH IN THE PRECEDING SENTENCE OF THIS SECTION 8
-ARE INCORPORATED INTO ANY AGREEMENT BETWEEN YOU AND YOUR CUSTOMERS OR
-LICENSEES. SYMANTEC SHALL NOT BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY
-DAMAGES CAUSED BY YOUR OR A THIRD PARTY’S CONTINUED USE OF ANY OUTDATED
-ROOTS FOR WHICH AN UPDATED VERSION IS MADE AVAILABLE BY SYMANTEC. FURTHER,
-UNDER NO CIRCUMSTANCES WILL SYMANTEC'S LIABILITY FOR ANY ACTION OR CLAIM EXCEED
-USD$1,000, REGARDLESS OF WHETHER SUCH ACTION OR CLAIM IS BASED IN CONTRACT,
-TORT, STRICT LIABILITY, OR OTHERWISE.
-9. TERM AND TERMINATION.
-9.1. Term. This Agreement shall become effective as of the earlier of, Your first use of the Root
-Certificates, and shall remain in effect until the earlier of (i) Your discontinued use of the Root Certificates;
-(ii) termination by either party under the terms of Section 9.2, below; or (iii) Symantec’s notice to You that
-Symantec is no longer providing Root Certificates for use.
-9.2. Termination for Default/Insolvency. Either party shall be entitled to terminate this Agreement in the
-event of a failure by the other party to perform any of its material obligations under this Agreement if such
-breach is not cured within thirty (30) days after receipt of written notice thereof from the non-defaulting
-party or within forty-eight (48) hours after receipt of such written notice if a breach by You may
-compromise the security of the Symantec Trust Network or other system. This Agreement shall terminate
-upon the election of and notice from a party to the other if the other party is adjudged insolvent or
-bankrupt, or the institution of any proceedings by or against the other party seeking relief, reorganization,
-or arrangement under any laws relating to insolvency, or any assignment for the benefit of creditors, or
-the appointment of a receiver, liquidator, or trustee of any of the other party's property or assets, or the
-liquidation, dissolution, or winding up of the other party's business.
-9.3. Effect of Expiration or Termination. Upon expiration or termination of this Agreement, except for a
-breach by You, You may continue to distribute the current version of Your Products which incorporate the
-Root Certificates. Any updates or upgrades thereto may not include the Root Certificates and You shall
-stop making copies of Root Certificates, shall stop including Root Certificates in Your Products, and shall
-stop using Symantec’s logos and trademarks. The provisions of Sections 3, 4.3, 5, 6, 7, 8, 9.3, and 10
-shall survive termination of this Agreement.
-10. GENERAL.
-10.1. Governing Laws. This Agreement and any disputes relating to the services provided hereunder shall
-be governed and interpreted according to each of the following laws, respectively, without regard to its
-conflicts of law provisions: (a) the laws of the State of California, if You are located in North America or
-Latin America; or (b) the law of England, if You are located in Europe, Middle East or Africa; or (c) the
-laws of Singapore, if You are located in Asia Pacific including Japan. The United Nations Convention on
-Contracts for the International Sale of Goods shall not apply to this Agreement.
-10.2. Binding Upon Successors; Assignment. This Agreement shall be binding upon, and inure to the
-benefit of, the successors, executors, heirs, representatives, administrators, and assigns of the parties
-hereto. Notwithstanding the foregoing, You may not assign Your rights or obligations under this
-Agreement without the prior written consent of Symantec. Any such purported assignment of this
-Agreement without obtaining written consent shall be void and of no effect.
-10.3. Severability; Enforcement; No Waiver. The unenforceability of any provision or provisions of this
-Agreement shall not impair the enforceability of any other part of this Agreement. If any provision of this
-Agreement shall be deemed invalid or unenforceable, in whole or in part, this Agreement shall be deemed
-amended to delete or modify, as necessary, the invalid or unenforceable provision to render it valid,
-enforceable, and, insofar as possible, consistent with the original intent of the parties. The failure of a
-party, at any time or from time to time, to require performance of any obligations of the other party
-hereunder shall not be deemed a waiver and shall not affect its right to enforce any provision of this
-Agreement at a subsequent time.
-10.4. Entire Agreement; Amendments; Waivers. This Agreement constitutes the entire understanding and
-agreement of the parties, whether written or oral, with respect to the subject matter hereof and supersede
-all prior and contemporaneous agreements or understandings between the parties. Any term or provision
-of this Agreement may be amended, and the observance of any term of this Agreement may be waived,
-only by writing signed by the parties to be bound thereby.
-10.5. Compliance with Law, Export Requirements and Foreign Reshipment Liability. Each party shall
-comply with all applicable federal, state and local laws and regulations in connection with its performance
-under this Agreement. Services, including documentation, may include controlled technology or technical
-data (collectively “Controlled Technology”) that is subject to the U.S. Export Administration Regulations
-(EAR), and diversion contrary to U.S. law is prohibited. You agree to comply with all relevant laws
-including the U.S. EAR and the laws of any country from which Controlled Technology is exported. All
-Controlled Technology is prohibited for export or re-export to Cuba, North Korea, Iran, Sudan and Syria
-and to any country or its nationals subject to relevant embargo or sanction or to any entity or person for
-which an export license is required per any relevant restricted party list, without first obtaining a license.
-Furthermore, You hereby agree that You will not use or allow use of Controlled Technology in connection
-with chemical, biological, or nuclear weapons, or missiles, drones or space launch vehicles capable of
-delivering such weapons. Symantec shall have the right to suspend performance of any of its obligations
-under this Agreement, without any prior notice being required and without any liability to Customer, if You
-fail to comply with this provision.
-10.6. Notices. You will make all notices, demands or requests to Symantec with respect to this Agreement
-in writing to the "Contact" address listed on the website from where you downloaded the Root Certificates,
-with a copy to: General Counsel – Legal Department, Symantec Corporation, 350 Ellis Street, Mountain
-View, California 94043, USA. Notices shall be effective on the date received (unless the notice specifies a
-later date) only if it is sent by a courier service that confirms delivery in writing or if sent by certified or
-registered mail, postage prepaid, return receipt requested. Symantec may post notices and updates
-regarding the Agreement or the Root Certificates at the URL provided to You for the Root Certificates.
-You shall be responsible for regularly checking the applicable URL for notices from Symantec regarding
-the Agreement or the Root Certificates. No notices, demands, or requests to Symantec with respect to
-this Agreement may be delivered by electronic mail. You shall immediately notify Symantec of any legal
-notices served on You that might affect Symantec, and shall promptly forward the original or a copy of
-such notice to Symantec.
-10.7. Independent Parties. The relationship between You and Symantec is that of independent
-contractors. Neither party nor its employees, consultants, contractors, or agents are agents, employees,
-or joint venturers of the other party, nor do they have any authority to bind the other party by contract or
-otherwise to any obligation.
-Root Certificate License Agreement v3.0 (January 2014)
-```
-<!-- licencestop -->

package/bin/ca-gen.js

@@ -1,91 +0,0 @@
-#!/usr/bin/env node
-
-/*
- * Copyright 2020 New Relic Corporation. All rights reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-
-'use strict'
-/* eslint-disable no-console */
-
-const fs = require('fs')
-const path = require('path')
-const glob = require('glob')
-
-const CERT_PATH = path.join(__dirname, '..', '..', 'SSL_CA_cert_bundle', '*.pem')
-
-const OUTFILE =
-  path.join(__dirname, '..', 'lib', 'collector', 'ssl', 'certificates')
-
-const HEADER =
-  `/**\n
-   * certificates.js - CA bundle for SSL communication with RPM.\n
-   *\n
-   * This file contains the X509 certificates used to communicate with New Relic\n
-   * over SSL.\n
-   */\n\n`
-
-class Certificate {
-  constructor(name, body) {
-    this.name = name
-    this.body = body
-  }
-
-  toEntry() {
-    let output = `  // ${this.name}\n`
-    const rawPEM = this.body.split('\n')
-
-    for (let i = 0; i < rawPEM.length; i++) {
-      const line = rawPEM[i]
-      // some Thawte certificates have Windows line endings
-      line = line.replace('\r', '')
-      if (line.match(/END CERTIFICATE/)) {
-        output += `  "${line}\\n"`
-        break
-      }
-      output += `  "${line}\\n" +\n`
-    }
-
-    return output
-  }
-}
-
-function loadCerts(root, callback) {
-  glob(root, (error, files) => {
-    if (error) {
-      return callback(error, null)
-    }
-
-    const certificates = []
-    console.log(`Loading ${files.length} certficates.`)
-
-    for (let i = 0; i < files.length; i++) {
-      const file = files[i]
-      const certificate = new Certificate(
-        path.basename(file, '.pem'),
-        fs.readFileSync(file, 'ascii')
-      )
-
-      certificates.push(certificate)
-    }
-
-    callback(null, certificates)
-  })
-}
-
-function dumpCerts(error, certs) {
-  if (error) {
-    console.log(`got ${error.message} reading certs--bailing out`)
-    process.exit(1)
-  }
-
-  fs.writeFileSync(
-    OUTFILE,
-    HEADER +
-    'module.exports = [\n' +
-    certs.map((cert) => cert.toEntry()).join(',\n\n') +
-    '\n]\n'
-  )
-}
-
-loadCerts(CERT_PATH, dumpCerts)

package/bin/cassandra-setup.sh

@@ -1,11 +0,0 @@
-#! /bin/bash
-
-# Copyright 2020 New Relic Corporation. All rights reserved.
-# SPDX-License-Identifier: Apache-2.0
-
-sudo apt-get install python openjdk-8-jre -y
-echo "deb http://www.apache.org/dist/cassandra/debian 311x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list
-curl https://www.apache.org/dist/cassandra/KEYS | sudo apt-key add -
-sudo apt-get update
-sudo apt-get install cassandra
-sudo service cassandra start