- Reside on the New Relic One platform, alongside your other New Relic dashboards and data.
- Feature visualizations that you've tailored specifically for your organization.
- Display data from any source you want, whether from a New Relic-monitored entity or data from another service or API.
To start building, go to our developer site.
New Relic One: a programmable platform
At New Relic, we strive to have an out-of-the-box user experience that provides optimal value for all users. But we also know that some organizations have unique business needs that can’t be met with our standard visualization options.
Now, we give you control over the fundamental building blocks of our New Relic One platform. Using the same tools our engineers use to build New Relic One, you can build custom applications that align with your unique organizational structure and business needs. If you know how to use React, GraphQL, and NRQL (our query language), building a simple application will take you only a few minutes.
Combined with our other offerings, New Relic can help you solve any data-driven challenge, no matter how complex. You can:
- Use our APIs to get data into New Relic from any source.
- Visualize that data in your custom New Relic One applications.
Requirements and security
For feature requirements and security considerations, see Requirements.
Features of custom New Relic One applications
If you can imagine it, you can build it on New Relic One. New Relic One is a programmable platform that lets you:
- Build React JS applications that reside in New Relic and that feature highly customized data visualizations and interactive interfaces.
- Modularly construct your application using our library of React components and example applications.
- Pull in New Relic data using NerdGraph (our GraphQL API)
- Pull in data from any service or database.
Overview of creation process
Before building an application on New Relic One, you'll want a clear idea of what problem you're trying to solve. Here are some typical steps involved in creating a New Relic One application:
- Decide on a data-driven problem you need to solve (that cannot already be solved by New Relic monitoring tools).
- Brainstorm the ways you might solve that problem using data visualization. Need ideas? See our library of example applications.
- Decide what data you will need. This can be any data in the world, whether from New Relic or from any service or API.
- Come up with a plan. Create diagrams for how you want that data to be visualized and analyzed.
- Start to build.
For quick-start instructions:
- Go to one.newrelic.com.
- Select Build a New Relic One application and follow the instructions.
This will create and locally serve a simple application visible on the one.newrelic.com home page.
To learn to build, go to our developer site.
What's in a New Relic One application?
Before building an application, it can help you to understand what components are called and how they work together:
- The application: A New Relic One application is made up of these parts:
- Nerdpack. A Nerdpack is the package that contains all the files required by your application. It contains two artifacts that you have control over: Nerdlets and the launcher.
- Nerdlet. A specific UI view or window. A Nerdlet can contain multiple visual elements, like charts, interactive fields, or tooltips. There can be one or more Nerdlets in a Nerdpack.
- Launcher. This is one way your application can be "launched." Launchers are located on the New Relic One home page. You can customize a launcher’s title, icon, and description. (You also have the option for your application to be opened from the entity explorer.)
- CLI. Our command line application, which you use to generate, locally serve, publish, and deploy your application.
- React JS components for displaying charts and UI components.
- Platform APIs: give you access to New Relic One platform functionality.
- NerdGraph. NerdGraph is New Relic's GraphQL API. NerdGraph is used to retrieve and display New Relic-stored data.
- NerdStorage. This is a storage database used to store Nerdlet configuration data, such as user-specific settings, favorited items, or other data that affects how Nerdlets display.
For an overview of the tools available, see our developer site.