What is programmability for New Relic One?

Programmability for New Relic One is the ability to create custom UI displays that you can view in New Relic One. This puts the full power of New Relic in your hands, enabling you to create any sort of view or display you’d like to see. You know best what information you need beyond the displays and dashboards available out of the box from New Relic. Now you can create and share those views. 

Along the lines of the data ingest capabilities, which make it easier to get custom data into New Relic and provide consistent data modeling, storage, and handling , the programmable UI makes it easier to view data in customized but consistent ways in New Relic.

 

Why build a New Relic One application?

A New Relic One application is a React application that you can build using our build tools, and that  lives on our New Relic One platform. New Relic offers custom chart and custom dashboard features, but some organizations need highly customized visualizations and interfaces that match their business structure and goals. That’s why we’ve given you access to the same tools our developers use and put the power of New Relic in your hands. 

When building your visualizations, you can use data from any source, whether it’s existing New Relic data, or data from any arbitrary service or API. 

We also offer a library of open source New Relic One apps that you can clone or fork and use as-is, or that you can use as the starting point for adding your own custom functionality.

For more about the benefits of creating your own apps, see Intro to New Relic One applications.

How should I get started building?

We’ve created some resources to help you get started with your own apps: 

I got a message that I haven’t accepted developer terms and conditions. What do I do?

1. Go to New Relic One and select Build your own application

2. Under the Quick start procedure, choose an account to create an API key for. You will be prompted to accept the terms and conditions.

My org doesn’t want to accept the T&Cs. Can I still build?

I’m serving locally but my app isn’t appearing in New Relic One. What do I do?

Some tips: 

  • Ensure you’re using the New Relic One URL that looks for locally served apps: one.newrelic.com/?nerdpacks=local

  • A Nerdpack’s UUID controls what account data it has access to, and what accounts can serve and deploy it. If you’re trying to serve an app you didn’t build (which would include open source apps), the UUID must be reset to be associated with your account. You can do this with the nr1 nerdpack:uuid --generate CLI command.

I’m having problems publishing and deploying. What can I do?

How do I extend my webpack config?

You can use our .extended-webpackrc.js file to extend the webpack 4 configuration. This allows you to add your own aliases, scripts, and configurations when locally serving or deploying your app. 

Some resources for learning more about webpack configuration: 

What is the New Relic One Catalog?

The catalog allows you to subscribe to apps using the platform UI, instead of the command line and GitHub.

How do I participate in the New Relic One Catalog early access program?

The New Relic One Catalog is in early access. If you'd like to join the EAP (early access program), contact us at DECO@newrelic.com and we'll help you get started. We'll also invite you to feedback sessions to provide input on your experience. We use this feedback to plan improvements and new features. 

What if I’ve already installed an app from GitHub and now have access to the New Relic One Catalog?

Because each deployment generates a unique UUID, you’ll need to label your current version with another name if you choose to install the New Relic One Catalog app version. For example, if you already cloned the Customer journeys app from the GitHub repo, launched it locally on your machine, and want to subscribe to another version of Customer journeys from the Catalog, make sure to rename the version that you cloned. This is to avoid losing any work and customization you’ve created from the original version.

If you’re trying to subscribe to an app from the New Relic One Catalog that you previously subscribed to via the CLI and the GitHub repo, you’ll need to unsubscribe the GitHub version so you don’t have duplicate launchers in New Relic One.

 

Why don’t I see the app I subscribed to from the New Relic One Catalog on my New Relic One home page?

We are currently working on being able to refresh the home page when a subscribe or unsubscribe action is made on an application through the New Relic One Catalog. Until this refresh is available, if you perform a hard refresh on the home page, you should see your changes reflected there.

The application you subscribed to from the New Relic One Catalog might not include a Launcher, in which case the application is likely specific to an entity type and will be available as a link from the left navigation menu when viewing that entity type in the entity explorer.

 

Who can use programmability features?

If you are a customer who pays for a Pro SKU, you have access to New Relic One. It is not priced separately and is able to use the programmability capabilities. Please note that creating custom UI requires knowledge of JavaScript and React.

 

What if I have an issue with my app or the Catalog?

New Relic hosts and moderates an online forum where you can interact with New Relic employees as well as other customers to get help and share best practices. Each app has a related topic in the New Relic Explorers Hub, and you will find blog posts, how tos, and other app related content there as well. This is your best first stop for troubleshooting help. You can submit defect reports or enhancement requests in GitHub, on the Issues tab for each app.