• EnglishEspañol日本語한국어Português
  • 로그인지금 시작하기

Cloud integrations release notesRSS

November 30, 2019
New Azure beta integrations

New

Three new Azure integrations have been released as beta:

October 2, 2019
AWS Trusted Advisor, Azure Cost Management integrations

New

Changes

  • Added new metrics for AWS ElastiCache Nodes
    • ActiveDefragHits
    • EngineCpuUtilization
    • StreamBasedCmds
  • Added the option of a 5min polling interval for the VPC integration

September 13, 2019
Azure Cost Management integration, new AWS RDS metrics

New

New Relic now offers a cloud integration with the Microsoft Azure Cost Management service. It provides the accumulated costs in the billing period, grouped by cloud service, resource group, region, and (if configured) custom tags. Learn more in the Azure Cost Management documentation.

Changes

Amazon AWS RDS cloud integration now has a couple of new metrics:

  • For each database engine: numVCPUs, uptime, diskIO, and device
  • For MS SQL engine only: memory, kernPagedKb, and process

For more information, see the AWS RDS monitoring documentation.

August 13, 2019
Updated AWS ELB integrations (ALB, NLB, ELB Classic)

New

Changes

  • Moved ALB and NLB integrations under the ELB section to align with AWS
  • Renamed ELB integration to ELB (Classic)

Minor changes

  • AWS RDS: All charts in the dashboard now FACETed by database name
  • GCP: You can now see the amount of SDK API calls we make in the GCP Status Dashboard

August 8, 2019
Azure Databases for PostgreSQL, MySQL, and MariaDB monitoring integration

New

Three new Azure Database integrations are now available:

Changes

The Azure Cosmos DB integration has been updated to gather metrics through the new Azure SDK. Details on all the new metrics can be found in the new Azure Cosmos DB integration documentation.

For information on deprecated Cosmos DB events and metrics, see Azure Cosmos DB integration (deprecated). We strongly recommend migrating to the supported events and metrics in the new Azure Cosmos DB integration.

July 1, 2019
More accessible menus and EC

New

  • By default, Infrastructure collects EC2 instance metadata that includes public and private IP addresses, and network interface details. Now the AWS EC2 monitoring integration includes a toggle not to store and display these IP data as inventory or Insights events metadata.

Changes

  • The New Relic Infrastructure menu structure has been updated to make it easier to navigate the data.

    • Now the three supported cloud providers tabs (AWS, Azure and GCP) are always visible in the Infrastructure navigation bar.
    • All metrics for hosts are now grouped under a Hosts section. Metrics related to system, network, storage, processes are accessible using new navigation tabs.
    • On-host services such as Nginx, MySQL or Redis are grouped under a new Third-party services navigation item, while the Kubernetes cluster explorer can be accessed from the Kubernetes tab.

June 18, 2019
New metrics for AWS Elasticsearch

New

  • The AWS Elasticsearch integration has been updated with new metrics for clusters.

    • You can now monitor the total number of requests to the cluster and the response codes; rates and latency for indexing and search requests; queued tasks in different thread pools, and errors related to encryption keys. Most of these new metrics are useful to decide whether a cluster needs to be scaled up.
    • Additionally, you can enable the collection of some of these metrics at the node level.
  • The regionName attribute has been added to the New Relic Insights events collected by the Azure SQL Database integration: AzureSqlDatabaseSample and AzureSqlElasticPoolSample.

    • This attribute can be used for grouping and filtering down results in NRQL queries, dashboards and alert conditions.

April 10, 2019
Bug fix for AWS Auto Scaling

Bug fix

Some AWS Auto Scaling entities had duplicate identifiers, causing some metadata to be missing or wrong. In order to fix this issue, New Relic has regenerated the internal externalKey attribute for all Auto Scaling entities in Insights events and Infrastructure inventory for this cloud integration.

This change doesn't have any impact either on the integration default dashboard provided by New Relic Infrastructure or on the Insights queries.

However, all entities related to AWS Auto Scaling will be created again in Inventory. Accordingly, once the fix is released in your account, you might see duplicated entities for 48 hours, until the old identifiers expire. This might also cause an unexpected volume of Entity created events.

March 29, 2019
Label collection for Google Cloud integrations

New

  • New Relic now collects labels for Google Compute Engine, Kubernetes Engine, Cloud SQL, and Cloud Functions services. They join BigQuery, Cloud Spanner, Cloud Pub/Sub, and Cloud Storage integrations, which were collecting labels already. With the appropriate permissions, you'll be able to use the following metadata to narrow down queries, dashboards, and alerts related to Google Cloud resources:
    • Labels for Functions.
    • Labels for SQL databases.
    • Labels for Kubernetes clusters, which are propagated to nodes, pods and containers. If you'd like entity specific labels to be collected, you can use the Kubernetes integration.
    • Labels and tags for Compute Engine virtual machines, and labels for disks. Tags are treated as a regular label with value true.
  • Additionally, Inventory for Google Compute Engine and Google Cloud Functions has been enhanced with new attributes and restructured, so it's easier to find the metadata that belongs to each entity.
  • The aforementioned improvements might cause an unexpected volume of Entity modified events, as Inventory will be updated with the new data.

March 28, 2019
Bug fixes for Google Cloud integrations

Bug fixes

  • Some Google Kubernetes Engine entities had duplicate identifiers. In order to fix this issue, New Relic has regenerated the internal entityId and externalKey attributes for all containers in Insights events and Infrastructure inventory for this cloud integration.

    • This change doesn't have any impact either on the integration default dashboard provided by New Relic Infrastructure or on the Insights queries.
    • However, all entities related to Google Kubernetes Engine will be created again in Inventory. Accordingly, you might see duplicated entities for 48 hours, until the old identifiers expire. This might also cause an unexpected volume of Entity created events.
  • Metadata for Google Compute Engine virtual machines was not being added to the metric events reported by the New Relic infrastructure agent. In order to fix this issue, New Relic has regenerated the internal externalKey attribute for all virtual machines and disks in Insights events and Infrastructure inventory for this cloud integration.

    • This change doesn't have any impact either on the integration default dashboard provided by New Relic Infrastructure or on the Insights queries.
    • However, all entities related to Google Compute Engine will be created again in Inventory. Accordingly you might see duplicated entities for 48 hours, until the old identifiers expire. This might also cause an unexpected volume of Entity created events.
  • For Google Cloud integrations, the value of the zone attribute was not reported consistently. As a consequence, some inventory attributes and event metadata, such as project, were not reported for some Google Cloud Storage buckets.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.