Cloud integrations release notesRSS

New for Amazon Web Services monitoring

• New Relic has optimized the way to fetch metrics from AWS CloudWatch. This has resulted in a significant reduction in the number of calls to your AWS CloudWatch service, as well as a reduction in data lag. The list of specific permissions that are required to fetch monitoring data from AWS services has been updated accordingly, with the additional cloudwatch:GetMetricData permission.
  Recommendation: Use a custom policy only when you are unable to use the ReadOnlyAccessmanaged policy from AWS. If you use a custom policy, be sure to check that the new permission is included.
• AWS Redshift integration now provides four new metrics to monitor the performance of multi-node clusters: QueriesCompletedPerSecond, WLMQueriesCompletedPerSecond, QueryDuration, and WLMQueryDuration. Check AWS Redshift integration for details.
• If you use AWS API Gateway, you can now fine-tune the data gathered for this service by specifying the stages you want to monitor with the new Filter by stage name prefixes. Check Configure polling frequency and data collection for cloud integrations for details.

New for Google Cloud Platform monitoring

• Google Kubernetes Engine integration is now available. If you're using Kubernetes v1.10.2 or later, now you can get visibility into containers, nodes, and pods. This cloud integration is complementary to New Relic's Kubernetes on-host integration.
• You can now link your GCP projects to New Relic using a service account. If you had already used a user account to link your projects, you can migrate to the new authorization type, though the UI. Check Connect Google Cloud Platform services to Infrastructure for details.

Changes in Google Cloud Platform integrations

• The default dashboards for Google Cloud Platform integrations now include a filter by Project ID. This is very useful if you monitor more than one project from the same Google Stackdriver Monitor service.

New

• If you're using Lambda@Edge to execute Lambda functions in AWS regions that are closer to your clients, you can get function execution location metadata by enabling the new Collect Lambda@Edge data filter in the AWS CloudFront integration.
• The status of AWS VPC Network Interfaces and AWS VPC Peering Connections is now available, both as an inventory attribute (status) and as metrics metadata (provider.status).
• The launch type of AWS ECS services is now available as an inventory attribute (launchType) and as metrics metadata (provider.launchType). It contains the type of infrastructure on which tasks and services are hosted (EC2 or FARGATE).

Changes

• The default dashboard for AWS ELB has been updated: the previous chart named "Healthy vs. Unhealthy Hosts" has been replaced by a new chart named "ELBs with no healthy hosts", which shows more accurately the number of elastic load balancers that are not able to send traffic to any healthy target.
• The default dashboard for AWS ALB has been updated: the previous chart named "Healthy vs. Unhealthy Hosts" has been replaced by a new chart named "Target Groups with no healthy hosts", which shows more accurately the number of target groups that don't have any healthy target host to send traffic to.

Tags and labels attribute renaming

In order to make it easier to find common attributes across different data providers in New Relic infrastructure, tags and labels attribute names are going to be renamed as label.<name>, where <name> is:

• The tag key for Amazon Web Services and Microsoft Azure integrations
• The label key for Google Cloud Platform integrations

The previous attribute names will be deprecated on June 21, 2018.

If you are using tags or labels in alerts, custom dashboards, or saved queries for New Relic cloud integrations, be sure to rename them using the new format before June 21, 2018.

Azure integrations: Resource group attribute renaming

To make it easier to find common attributes across different cloud services, the resourceGroup attribute will be replaced by the resourceGroupName attribute on June 21, 2018. This affects Infrastructure integrations for:

• Azure Virtual Machines
• Azure Service Bus
• Azure Virtual Networks

If you are using the resourceGroup attribute in alerts, custom dashboards, or saved queries for these Azure services, be sure to rename them using the new format before June 21, 2018.

Amazon Web Services S3 permissions

The list of specific permissions that are required to fetch monitoring data from AWS S3 service has been updated with the additional s3:GetMetricsConfiguration permission in integrations and managed policies.

Recommendation: Use a custom policy only when you are unable to use the ReadOnlyAccess managed policy from AWS. If you use a custom policy, be sure to check that the listed permissions are included.

New

• New Relic Infrastructure can now collect metrics and inventory data from Google Cloud Platform services. The first integrations available are Google Compute Engine, Storage, Functions and App Engine. This feature is in beta. For more information, see Introduction to Google Cloud Platform integrations.

New

• AWS IoT integration is now available. Check AWS IoT monitoring integration for details.
• AWS EMR integration is now available. Check AWS EMR monitoring integration for details.
• AWS Health integration is now available. Check AWS Health monitoring integration for details.
• AWS CloudTrail integration is now available. Check AWS CloudTrail monitoring integration for details.
• Azure Redis Cache integration is now available. Check Azure Redis Cache monitoring integration for details.