Configure polling frequency and data collection for cloud integrations

New Relic Infrastructure cloud integrations report the maximum amount of data by default (with the exception of shards data collection). The default settings are:

If you require more or less data from your cloud integrations, you can change the configuration settings to modify the amount of data they report. Changing the configuration settings for your integrations may impact alert conditions and chart trends.

Anyone with access to an Infrastructure account can view the data reported to that account. Only Owners, Admins, and Infrastructure add-on managers can manage the integrations.

Change polling frequency

The polling frequency configuration determines how often New Relic reports data from your cloud provider. By default, the polling frequency is set to the maximum frequency that is available for each service.

To change the polling frequency for your cloud integration:

  1. Go to infrastructure.newrelic.com > Integrations.
  2. Select the tab that corresponds to your cloud service provider.
  3. Select Configure next to the integration.
  4. Use the dropdowns next to Metrics data and Inventory data to select how frequently you want New Relic to capture your cloud integration data.

You might have business reasons why you would want to manage your polling frequency, such as:

  • If you need to manage your AWS CloudWatch bill, you may want to decrease the polling frequency. Before you do this, make sure that any alerts conditions set for your cloud integrations are not affected by this reduction.
  • If you are deploying a new service or configuration and you want to collect data more often, you may want to increase the polling frequency temporarily.

Filter data

By default, no filters are selected and extended inventory is On, so the integration reports the maximum amount of data, except for shards data collection. You can apply multiple filters to each integration in order to specify which information you want captured for your cloud integration.

To change the filters for your cloud integration:

  1. Go to infrastructure.newrelic.com > Integrations.
  2. Select the tab that corresponds to your cloud service provider.
  3. Select Configure next to the integration.
  4. Turn the filters you want On and select or enter the values that you want included in your reported data.
  5. Turn extended inventory or shards data collection to On or Off.

There are different filters available, depending on the integration. The filters available for your integration are listed under Data collections and filters on the Configure page for your integration.

Filter Description
Region Select the regions that include the resources that you want to monitor.
Queue prefixes

Available for AWS SQS integration.

Enter each name or prefix for the queues that you want to monitor. Filter values are case-sensitive.

Load balancer prefixes

Available for AWS ALB integration.

Enter each name or prefix for the application load balancers that you want to monitor. Filter values are case-sensitive.

Stage name prefixes

Available for AWS API Gateway integration.

Enter each name or prefix for the stages that you want to monitor. Filter values are case-sensitive.

Tag key Enter one tag key that is associated with the resources that you want to monitor. Filter values are case-sensitive, and you can use this filter in combination with tag value filter.
Tag value Enter one tag value that is associated with the resources that you want to monitor. Filter values are case-sensitive, and you can use this filter in combination with tag key.
Resource group

Select the resource groups that are associated with the resources that you want to monitor.

Collect extended inventory

Available for AWS EBS integration.

By default, your AWS EBS integration makes API calls to report autoEnableIo inventory data. Switch this to Off if you don't want to monitor autoEnableIo inventory.

Collect shards data

Available for AWS Kinesis Streams integration.

By default, Infrastructure does not report shard metrics. Switch this to On if you want to monitor shard metrics in addition to data stream metrics.

Collect Lambda@Edge data

Available for AWS CloudFront integration.

By default, Infrastructure does not report Lambda@Edge data. Switch this to On if you're using Lambda@Edge in AWS CloudFront and want to get Lambda execution location metadata.

Collect NAT Gateway data and Collect VPN data

Available for AWS VPC integration.

By default, Infrastructure does not report NAT Gateway nor VPN metrics. Switch these to On if you want to monitor NAT Gateway and VPN metrics and inventory, in addition to other VPC related entities inventory.

Potential impact on alerts and charts

If you change an integration's configuration, it can impact alert conditions and charts. Here are some things to consider:

If you change this configuration setting... It may have this impact...
Any configuration setting When you change the configuration settings, the data that New Relic displays in Infrastructure charts, on the inventory page, and in the events feed changes as well.
Any filters When you create alert conditions after you set filters, make sure that your alerts are not triggered by resources that you filtered out.
Filter for regions

If you filter for specific regions, it may lower the amount of data reported to New Relic, which could trigger an alert.

If you create an alert condition for a specific region and then filter that region out, the region would no longer report data and would never trigger the alert.

Polling frequency When you create an alert, make sure that you define the threshold for a time period that is longer than the polling frequency.
Extended inventory If you turn off extended inventory, Infrastructure makes fewer API calls to AWS, which could reduce your AWS CloudWatch usage bill, but autoEnableIo inventory data will no longer be captured.

For more help

Recommendations for learning more: