New
Three new Azure integrations have been released as beta:
- [Beta] Azure API Management
- [Beta] Azure SQL Managed instances
- [Beta] Azure Virtual Machine Scale Sets
New
- AWS Trusted Advisor integration
- New Relic now offers an integration with AWS Trusted Advisor. AWS establishes limits for each service in each account and region. Some examples are: number of Auto Scaling groups, number of EBS active volumes, and number of EC2 elastic IP addresses. AWS recommends watching these limits, and even allows you to enable automated actions and custom notifications. That data is now also available in New Relic.
- For more information on how to enable the integration, check out the integration documentation.
- Azure Cost Management integration
- New Relic now offers a cloud integration with the 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.
- For more information on how to enable the integration, check out the integration documentation.
Changes
- Added new metrics for AWS ElastiCache Nodes
- ActiveDefragHits
- EngineCpuUtilization
- StreamBasedCmds
- Added the option of a 5min polling interval for the VPC integration
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
, anddevice
- For MS SQL engine only:
memory
,kernPagedKb
, andprocess
For more information, see the AWS RDS monitoring documentation.
New
- Added support for AWS Network Load Balancers (NLBs)
- Added two Entity Types to New Relic: ELB network load balancer, ELB network target group
- Added more metrics for AWS Application Load Balancers see the documentation for the full list.
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
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.
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.
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
andAzureSqlElasticPoolSample
.- This attribute can be used for grouping and filtering down results in NRQL queries, dashboards and alert conditions.
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.
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.
Bug fixes
Some Google Kubernetes Engine entities had duplicate identifiers. In order to fix this issue, New Relic has regenerated the internal
entityId
andexternalKey
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 asproject
, were not reported for some Google Cloud Storage buckets.