After releasing more than 30 cloud-service integrations and seeing how our customers are using them, we learned that while monitoring relevant cloud services is a high priority, getting a focused view is equally important—as is avoiding significant increases to their cloud usage bill.

Keeping that in mind, we are excited to announce a super easy way to get granular control over monitoring Amazon Web Services and Microsoft Azure cloud services.

Fine-grained control that is easy to configure

The new ability to configure polling frequency and data collection for cloud integrations is designed to let New Relic customers

  • Reduce the polling intervals for metrics and inventory
  • Set filter conditions to narrow data fetching (for example, by region or by tag)

In addition, this fine-tuning can be configured individually for each cloud integration with a few clicks in the UI, as seen below:

polling frequency chart: cloud service monitoring

We built this new functionality to help customers focus on the cloud service data that is important to them, and to help prevent the potential implications of excessive API polling, including hitting API usage rate limits and unnecessarily incurring additional service charges.

Configuration options

The new feature can be found in the New Relic Infrastructure user interface for each integration, and can be used to granularly configure the following:

  • How often New Relic gathers service metrics from the cloud provider
  • How often New Relic gathers cloud entities and services attributes from the cloud provider
  • Which specific locations or resource groups will be monitored
  • Which tag keys or tag values describe the resources to be monitored
  • The name of the resources (such as AWS queues and application load balancers) to be monitored

You can filter not only by service and region, but also by customer-defined tags that match the way you want to monitor your environment. For example, you could filter by production versus development environments, or by application type or any other filter set you define. Once you turn on the filter, you should notice a difference in the amount of data that is being fetched.

new relic insights graph: cloud service monitoring

This graph from New Relic Insights shows the effect of filtering Microsoft Azure virtual machines by resource group. For one hour we set the filter to gather only the VMs that belong to resource group RG1.

The ability to configure polling frequency and data collection for cloud integrations is now available for most AWS and Azure services for customers with a New Relic Infrastructure Pro subscription. See the documentation for more details.


Chhavi Nijhawan is a senior product marketing manager at New Relic. She is passionate about new technologies. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!