This document contains:
- Requirements for building a New Relic One application
- Details on application/data access and permissions
- Support details
Requirements and recommendations
- Access to one.newrelic.com (New Relic One requires a paid New Relic account and use of a supported browser)
- A personal New Relic API key (generated as part of quick-start procedure)
- Node v10 or higher
- A GitHub account
To help you build your application, it will help (but is not required) to be familiar with:
Some details on New Relic One application support:
- For common questions and answers about building, see the Explorer's Hub page on building on New Relic One.
Data security and data access
Some notes on how data security is handled for New Relic One applications:
- The ability to publish and deploy an application to an account requires a Nerdpack Manager add-on role, which can be assigned by New Relic account Owners and Admins.
- For details on how access to New Relic One applications and data is determined, see our developer site.
- Third-party libraries may be included at runtime by Nerdpacks. Changes to the content of these libraries may not be reflected in version number updates to the Nerdpack itself (for example, if a Nerdlet creates a
<SCRIPT>tag and dynamically downloads and executes an external file).