Cloud Integrations Release Notes

Thursday, January 10, 2019 - 00:00

New: Enable or disable attribute collection via UI

You can enable or disable the collection of extended inventory attributes through New Relic's user interface for AWS Application Load Balancer (ALB), Elastic Load Balancer (ELB), Elastic Beanstalk, Elastic Block Store (EBS), Route53 and Simple Notification Service (SNS). This tool helps you reduce the amount of calls that New Relic does to AWS APIs, and it might contribute to contain your AWS bill. For more information, see the documentation for:

  • Configuring the polling frequency of data collection through the Infrastructure integrations UI
  • Attributes that make part of extended inventory in each cloud integration

New: View errors fetching data via UI

Also, the cloud integrations Account status dashboard shows any errors New Relic might experience when trying to fetch inventory and metric data for your cloud resources. The Fetching errors chart now shows the cloud service these resources belong to. This will help to facilitate troubleshooting the integration setup.

Friday, November 30, 2018 - 00:00

Changes in curated dashboards

New Relic Infrastructure integrations will not automatically create new dashboards in New Relic Insights when an integration is enabled.

Instead, curated dashboards for On-host and Cloud integrations data will be embedded in the New Relic Infrastructure UI, and they can be reached from the following links:

  • On-host integrations:
    https://infrastructure.newrelic.com/accounts/<your_account_ID>/integrations/onHostIntegrations

  • AWS integrations:
    https://infrastructure.newrelic.com/accounts/<your_account_ID>/integrations/aws

  • Azure integrations:
    https://infrastructure.newrelic.com/accounts/<your_account_ID>/integrations/azure

  • GCP integrations:
    https://infrastructure.newrelic.com/accounts/<your_account_ID>/integrations/gcp

Please refer to the transition guide and the Infrastructure integration dashboards and charts documentation for more details about the new pre-built integration dashboards.

Note the existing curated dashboards that had been automatically created in New Relic Insights through the InfrastructurePro@newrelic.com user are still available. These dashboards won't be automatically updated anymore, but now you can edit and remove them. By default, they have the same name as the dashboard in New Relic Infrastructure, that takes this format:

  • For on-host integrations: <Integration name>

  • For cloud integrations: <Integration name> - <Linked account name>

Other changes

  • The former systemErrors metric in the AWS DynamoDB integration is now reported in several different metrics which represent the total number of requests that generate an HTTP 500 status per operation type. Please refer to AWS DynamoDB monitoring integration for details.

New

Friday, October 19, 2018 - 00:00

New

  • It's now possible to filter by tags in the Infrastructure default dashboards. In the filter, tag keys and values are grouped under the Labels category so they can be more easily found.

  • The AWS ALB integration now collects tags for ALB Target Groups that can be used in NQRL queries and dashboard filters. You can also fine-tune the data gathered with this integration by specifying the resource tag key and value you want to monitor with the new Filter by tag. Please refer to Configure polling frequency and data collection for cloud integrations for details.

  • The AWS API Gateway integration now collects tags for stages, resources and methods, which can be used in NQRL queries and dashboard filters.

  • The AWS Redis Cache integration now collects the OperationsPerSecond metric, which reports the number of commands processed per second by the cache server.

Changes

  • The threshold selector in Infrastructure Integrations Alerts now includes the metric unit, so it's much easier to configure the correct threshold value. It is available for RDS metrics, and shall be available in other services soon.
  • The BucketSizeBytes metric for AWS S3 buckets was returning only the size of Standard Storage objects contained in the bucket. Now the metric returns the aggregated size of all storage types. Note the BucketSizeBytes metric is included in the DatastoreSample event type with a provider value of S3Bucket.
Wednesday, September 5, 2018 - 10:00

New

  • The AWS EC2 integration now collects status check results in ComputeSample events: provider.statusCheckFailed, provider.statusCheckFailedInstance, and provider.statusCheckFailedSystem. These checks are performed by AWS EC2 periodically and help identify hardware and software issues on running EC2 instances. Check AWS EC2 integration for details.

  • The AWS VPC integration can now provide metrics for NAT Gateways and VPN Tunnels. To collect data about these entities, please enable the corresponding filter in the integration configuration. Check AWS VPC monitoring integration for a description of AWS VPC related events and entities, as well as their metrics and attributes.
  • The AWS ALB integration now collects tags for ALB Target Groups that can be used in NQRL queries and dashboard filters. You can also fine-tune the data gathered with this integration by specifying the resource tag key and value you want to monitor with the new Filter by tag. Check Configure polling frequency and data collection for cloud integrations for details.

Changes

  • If you had enabled the AWS VPC integration and you want to keep collecting NAT Gateway inventory data, please enable the filter under the integration settings. Take into account that New Relic will also start collecting NAT Gateway metrics from that moment on, and you might notice an increase in the number of calls to AWS CloudWatch.
  • The AWS S3 metric BucketSizeBytes has changed to reflect all storage types. Now, this metric includes the sum of the amount of data in bytes stored in a bucket including Standard Storage, Reduced Redundancy Storage, Infrequent Access Storage (IAS), One zone IAS, and Glacier Storage including overheads. As a result, you might see an increased total number of bytes for that metric.
Friday, July 20, 2018 - 00:00

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.
Friday, July 6, 2018 - 00:00

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.
Wednesday, May 30, 2018 - 00:00

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.

Thursday, April 12, 2018 - 00:00

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.
Monday, April 9, 2018 - 00:00

New

Saturday, March 31, 2018 - 00:00

New Relic is now publishing release notes for Cloud Integrations. Stay up to date by subscribing to the RSS feed.

New

  • The AWS Lambda integration can now be monitored in these additional regions: South America (Sao Paulo/sa-east-1), Asia Pacific (Mumbai/ap-south-1), Canada (Central/ca-central-1) and EU (London/eu-west-2).

Changes