• /
  • Log in
  • Free account

Identify issues and roadblocks

As you migrate your applications to the cloud, you want to catch and correct any unexpected behavior or outcomes as soon as possible. Detecting errors and issues related to your new cloud architecture, performance, and scale is critical—getting the right information at the right time can be the difference between success and failure.

1. Identify components

Create a list all of applications, services, and their underlying server infrastructures in your application portfolio that you want to migrate to the cloud.

2. Identify KPIs

To provide quantifiable measures that your teams can use to assess your migration, identify a list of corporate KPIs (key performance indicators). Using the New Relic platform to measure KPIs helps you eliminate blindspots and see the connections between entities—from your application code, to your cloud infrastructure (including containers running in highly distributed microservices), to your customer experience. Your goal is to create a collection of metrics in several categories that you can visualize in our Dashboards.

To validate cloud improvements, group KPIs in the following categories, from least to most strong:

  • Application and infrastructure performance
  • End-user experience, including website and mobile application performance
  • Audience and content trends
  • DevOps productivity
  • Application revenue analytics
  • Future business goals

3. Deploy monitoring tools

To start monitoring your KPIs, verify that the applications that you want to migrate are compatible with the requirements for the New Relic products you will use. Then, install the New Relic agents:

Set up alerts

New Relic Alerts is a single integrated solution with a centralized UI to help you focus on the metrics that you care about most. When you set up New Relic Alerts and NRQL alerting, you establish flexible policies and conditions to receive alerts and notifications on multiple channels (email, Slack, OpsGenie, etc.).

For more detailed information about creating, managing, and using alerts, check out the New Relic University tutorials.

4. Set up cloud integrations


Cloud-based integrations available through New Relic include Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform.

Once your applications are migrated to the cloud and you start to integrate new cloud services, you can use New Relic to monitor and report data about your cloud services, offering you a comprehensive view of your entire architecture in one place. For example, to capture and record AWS account activity for audit and governance purposes, use the New Relic AWS CloudTrail integration.

Tracking error events gives you awareness about API calls and services that have failed, while console logins help you monitor console activity and potential intrusion attempts. New Relic collects this event data so you can display it in a Dashboard or alert on it with NRQL.

To gain extended visibility into applications that your code depends on, you can also deploy on-host integrations for commonly used application components, such as MySQL, Apache, and NGINX. In addition, you can create your own custom on-host integration with the New Relic Integrations SDK.

5. Identify issues and roadblocks

Once your applications are running in the cloud, they may generate new types of errors that are different from the errors that they generated when running on-premise. You can use New Relic APM and browser monitoring to view error events, error metrics, and detailed error traces for your applications. If an error or unhandled exception happens, the data appears on the JavaScript errors page and the APM Error analytics page. From these pages, you can quickly troubleshoot runtime errors. Then, further analyze errors by grouping them according to attributes, by filtering them, or by searching for keywords in the event data.

Each unhandled exception generates a transaction error event in Insights, and the dashboards are updated in real-time. Event data is a record of a single event at a particular moment in time and consists of default attributes, like a timestamp, and an event type. You can also add custom attributes to provide more context.


Once you start capturing JavaScript errors as events in Insights, set up NRQL alerting so you can stay on top of your error data.

Use the JavaScript errors page to get visibility into real-time user experience:

JavaScript errors page

one.newrelic.com > Browser > (select an app) > JS errors: Use the charts on this page to get visibility into the real-time user experience.

Then, create a Dashboard that covers a longer period of time and aligns the error and unhandled exception data with your KPIs:


one.newrelic.com > Dashboards > Create a dashboard: Use dashboards to align the error and unhandled exception data with your KPIs.

Expert tip for alerting on JavaScript errors

To get notifications for error spikes that are different from known or common JavaScript errors, use the following NRQL query for browser-monitored:

SELECT count(*) FROM JavaScriptError WHERE appName = '<BrowserAppName>' AND errorClass NOT IN ('<ErrorClass1>','<ErrorClass2>')
  • Replace <BrowserAppName> with the browser app name that you want to monitor with this alert.
  • Replace <ErrorClass1> and <ErrorClass2> with the on-premise error class names that you do not want New Relic to alert you about.
  • Set the threshold based on your alerting needs.

Using this query, New Relic alerts you every time a JavaScript error occurs when it has an error class that is not normally reported.

For more help

If you need more help, check out these support and learning resources:

Create issueEdit page
Copyright © 2021 New Relic Inc.