• /
  • Log in

Validate cloud improvements

After you migrate your applications to the cloud and integrate cloud services, use New Relic to measure and validate improvements to your applications.

1. 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 blind spots 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 dashboards in New Relic 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

2. 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 want to use. Then, install the New Relic agents:

3. Gather custom data

To manage, search for, and filter resources, assign metadata to your cloud resources in the form of tags. Tags are labels that consist of key-value pairs that you use to annotate your Infrastructure data.

Tag formats are different between AWS, Azure, and Google. Google, for example, has the shortest allowable lengths for keys and values. In addition, they all have different requirements for case sensitivity and allowable characters. To make sure that your tags are usable across most cloud providers:

  • Use only lowercase letters, numbers, underscores, and dashes.
  • Keep keys and values under 63 characters.

New Relic reports data contained in specific events to your account as part of its “out-of-the-box” functionality. You can add additional data to those events by using custom attributes. If you determine that you need to collect custom data, review custom data requirements, and report custom event data.

For more detailed information about sending custom data, check out these New Relic University tutorials:

4. Create baselines

In order to validate the value of moving to the cloud, you need to get baselines for your applications before you move to the cloud. Define pre-migration baselines for applications and their underlying infrastructures that you have designated for cloud service improvements based on your KPIs. To stay on top of your KPIs as you are moving, create baseline alerts for applications monitored by APM and browser and use NRQL alerts to get notified on any spikes or drops in your KPIs.

The following dashboard tracks key performance indicators for applications designated to move to the cloud:


one.newrelic.com > Dashboards > Create a dashboard: Create dashboards to track your KPIs.

After you migrate applications to the cloud, apply the same criteria to post-migration baselines so you can compare your results from before and after your migration.

5. Validate improvements with Dashboards

Dashboards is a single location to view all the data that New Relic products gather. Use New Relic Dashboards to visualize your KPIs before and after your move:

The following dashboard shows KPI data used to validate cloud improvements:


one.newrelic.com > Dashboards > Create a dashboard: Create dashboards to track your KPIs pre- and post-migration.

Use dashboards to validate the value of adopting a new cloud service and to answer key questions about application performance and customer experience.

For more help

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

Create issueEdit page
Copyright © 2021 New Relic Inc.