Cloud integrations release notesRSS

Update

• A new setting Keep legacy metadata has been added in the AWS EC2 polling integration, disabled by default for new integrations.
• When disabled, legacy attribute formats for EC2 metadata and custom tags will no longer be used. This helps reduce the data ingest quota when those legacy attribute formats are not used in custom dashboards or alert conditions.

New

• The AWS Health integration events are now stored as New Relic events (previously they were inventory data only).
• They can now be easily queried, added to dashboards, and included in alert conditions.

Update

• The AWS ECS integration has been updated with additional metrics for container instances.
• See all available ECS metrics in the AWS documentation.

New

• Amazon CloudWatch Metric Streams is a new way to send metrics for all AWS services and custom namespaces to New Relic. Learn more from the following resources:
  • New Relic blog post
  • AWS News blog
  • New Relic Product Documentation

Update

• It's now possible to update the Azure application's name and authentication credentials using the infrastructure UI or the cloud integrations API at any time. Learn how to update application details and rotate client secrets.

New

• The following integrations are now stable (v1.0):
  • AWS Kinesis Data Analytics
  • AWS Elemental MediaCovert
  • AWS FSx
  • AWS Elemental MediaPackage VOD
  • Azure Firewalls
  • Azure Service Fabric
  • Azure Application Gateway
  • Azure Key Vault
  • Azure Power BI Dedicated capacities

Improvements

We are upgrading our Infrastructure Cloud Alerting to use the New Relic Streaming Alerts backend. While you will not see any changes to the frontend UI or API, the backend implementation is moving to our new streaming alerts pipeline, with streaming algorithms that are specifically tuned for polling based cloud integrations.

As a result, your Infrastructure Cloud Alerts should have a significantly improved time-to-detect (they will be faster), with increased reliability and accuracy. The latency between when your data is retrieved from the cloud provider, and when it is evaluated by the alerts engine should be less than 1 minute. However, we can not improve the time it takes for the cloud provider to return the data to us.

This rollout begins on 11/12/2020, and is targeted to complete by 11/24/2020. There will not be any visual indication when your individual accounts have been migrated. They will just start to perform better. If you experience any issues, please contact customer support or your account team.

New

• The following integrations are now available in beta:
  • AWS Kinesis Data Analytics
• New statistics for AWS ALB and AWS ELB:
  • aws.applicationelb.target_response_time.p90
  • aws.applicationelb.target_response_time.p95
  • aws.applicationelb.target_response_time.p99
  • aws.elb.latency.p90
  • aws.elb.latency.p95
  • aws.elb.latency.p99
• AWS ElasticCache Redis Nodes are now decorated with customer tags.

New

• The following integrations are now available in beta:
  • AWS Elemental MediaConvert
  • Azure Firewalls
  • Azure Service Fabric
  • Azure Key Vault
  • Azure Application Gateway