• /
  • EnglishEspañolFrançais日本語한국어Português
  • ログイン今すぐ開始

Migrate from API Polling to CloudWatch Metric Streams

For seamless integration of your AWS account with New Relic, Integration via CloudFormation and CloudWatch metric stream is the most recommended approach. However, if you have already integrated your AWS account with New Relic using API Polling, refer to the following procedure to migrate from API Polling to CloudWatch Metric Streams.

Prerequisites

Before you begin integrating your AWS account with New Relic, ensure that you meet the following prerequisites:

Migrate to the CloudWatch Metric Streams integration

You can migrate from API polling by creating a CloudFormation template, or by re-adding your AWS account and following our in-app guided install procedures. We recommend that you use the CloudFormation template method, as it's the most efficient way to migrate. These integrations are not supported by CloudWatch Metric Streams and can't be migrated to our integration:

  • AWS CloudTrail
  • AWS Health
  • AWS Trusted Advisor
  • AWS X-Ray

If you use these integrations, you still need to use the API polling method.

Our CloudWatch Metric Streams integration uses the Metric API to push metrics in the dimensional metric format. Our API polling method, on the other hand, pushes metrics based on events.

  • To assist in the transition, we provide a shimming mechanism that transparently lets you write queries in any format. These queries are processed as expected based on the source that's available, either from events to metrics or metrics to events.
  • We recommend reviewing some limitations about the shimming mechanism that lets you use event-based queries with the CloudWatch Metric Stream integration.

After migrating, some of New Relic features that depend on your API polling data may behave differently:

  • Dashboards: Custom dashboards that use poll-based AWS integration events will still work as expected.
  • Alerts: Alert conditions that use poll-based AWS events will still work. We recommend adapting those to the dimensional metric format that uses NRQL as source.
  • Entities: Your list of monitored entities might show duplicated entities for up to 24 hours.
  • Attributes: Poll-based AWS integrations prefix collected resource tags with label., while the AWS CloudWatch Metric Streams integration prefixes collected resource tags with tags.. If both integrations are enabled for the same AWS account, resource tags will appear under both prefixes when using the Event format.

Validate that your data

To confirm you're receiving data from the Metric Streams, follow these steps:

  1. Go to one.newrelic.com > All capabilities > Infrastructure > AWS. Search for the AWS account you've connected to New Relic. Stream accounts.
  2. Check the account status dashboard and confirm that New Relic receives the metric data. This may include errors and number of namespaces and metrics ingested.
  3. Explore your data by writing queries for specific sets of metrics.

It may take a few minutes for New Relic to detect new resources and synthesize them as entities.

ヒント

AWS CloudWatch metrics for global services, such AWS Billing, are only available in the us-east-1 region. Make sure there's an active CloudWatch metric stream configured in that region.

Collect data from multiple AWS accounts

Learn how to collect data from multiple AWS accounts.

AWS integrations metrics

Explore and use metrics from CloudWatch Metric Stream.

AWS integrations via CloudFormation and CWMS

Integrate AWS services with New Relic using CloudFormation and CloudWatch Metric Streams.

AWS integrations via CloudFormation and API Polling

Integrate AWS services with New Relic using CloudFormation and API Polling.

AWS integrations via Terraform

Integrate AWS services with New Relic using Terraform.

Manual integrations from AWS console

Manually integrate AWS services with New Relic from AWS console.

Copyright © 2025 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.