Cloud Integrations release notes

Cloud Integrations release notes

Thursday, April 30, 2020 - 04:45

Changes

  • AWS SES integration is now enabled for all new regions
Tuesday, April 21, 2020 - 08:15

Bug fixes

A bug affecting the Service Plan entity of the Azure App Service has been fixed. The following metrics have been renamed as a result:

  • sent has been renamed DiskQueueLength
  • received has been renamed HttpQueueLength

All other metrics stay the same.

For more information, see the Azure App Service Documentation.

Tuesday, March 31, 2020 - 04:30

New

Bug fixes

  • Fixed a bug that made the S3 integration stop fetching the bucketSizeBytes metric
  • Fixed a bug that prevented the S3 integration from fetching data for some buckets in regions other than us-east-1

Changes

  • Extended inventory is now disabled by default for all newly configured integrations
  • Decreased AWS IAM polling frequency to once every 60 minutes for all users. Default has been set to 60 minutes; more frequent polling is still possible by overriding the value
Saturday, February 29, 2020 - 04:30

New

Friday, January 31, 2020 - 04:30

New

Bug fixes

  • Fixed vulnerability in the GCP integrations registration workflow
Tuesday, December 31, 2019 - 04:30

New

Saturday, November 30, 2019 - 04:15

New

Three new Azure integrations have been released as beta:

Wednesday, October 2, 2019 - 07:00

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
Friday, September 13, 2019 - 02:45

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.

Tuesday, August 13, 2019 - 00:00

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

Thursday, August 8, 2019 - 02:45

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.

Monday, July 1, 2019 - 00:00

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.

Tuesday, June 18, 2019 - 00:00

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.

Wednesday, April 10, 2019 - 00:00

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.​

Friday, March 29, 2019 - 00:00

New

    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.
Thursday, March 28, 2019 - 00:00

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.
Wednesday, March 13, 2019 - 00:00

New

The account status dashboard for cloud-linked accounts introduces some significant changes:

  • The Account changes chart lists any action that was performed on the linked cloud account configuration, from linking, renaming and enabling cloud services for monitoring, to modifying the polling intervals or any other data collection option.
  • The charts in the dashboard have been reorganized to better understand API call usage, errors that affect New Relic collecting data, and changes to the integrations configuration.
  • For Google Cloud-linked projects, the dashboard now includes the Stackdriver calls chart, which shows the amount of API calls that New Relic sends to the Google Stackdriver Monitoring API.
Tuesday, March 12, 2019 - 00:00

New

  • In order to optimize the volume of calls to AWS APIs, the cloud integrations setting options have been enhanced. In particular:
    • New Relic will be using the same polling interval for metrics and inventory data from now on.
    • Many options for you to control the amount of inventory data that New Relic collects from your cloud account have been added: tags, extended inventory, regions, entity name prefixes, resource groups, etc. Please find which attributes are fetched by enabling extended inventory in the specific document for each cloud integration.
  • You can enable or disable the collection of extended inventory attributes through New Relic's user interface for AWS DynamoDB, AWS ElastiCache and Google Cloud BigQuery.
  • The AWS Lambda integration has been extended with additional metrics and inventory attributes:
    • The ServerlessSample event type now includes deadLetterErrors and iteratorAge metrics, both for functions and function aliases. Additionally, it includes the concurrentExecutions metric for functions that have a custom concurrency limit specified.

    • For functions, inventory (under aws/lambda/function/) now includes the kmsKeyArn, masterArn, revisionId and layers attributes.

    • For function aliases, inventory (under aws/lambda/alias/) now includes the revisionId and routingConfig attributes.

    • For mappings between an AWS resource and a function, inventory (under aws/lambda/event-source-mapping/) now includes the stateTransitionReason attribute.

Bug fixes

  • Google BigQuery tables with no schema were lacking some inventory attributes.​
Thursday, February 28, 2019 - 00:00

New

  • Google Cloud Load Balancing integration is now available. New Relic collects metrics for all types of load balancers, and provides a curated dashboard with successful requests, error percentages, throughput, and latency. Check Google Cloud Load Balancing monitoring integration for details.
  • Google Cloud Pub/Sub integration is now available. New Relic collects metrics and inventory data for Pub/Sub Topics and Subscriptions. Check Google Cloud Pub/Sub monitoring integration for details.
  • Google Cloud Spanner integration is now available. New Relic’s curated dashboard shows relevant metrics for Spanner instances and databases, such as request latency, disk, CPU, successful requests count and error rate. Check Google Cloud Spanner monitoring integration for details.
  • Google Cloud SQL is now available. The most relevant metrics to watch are CPU, memory and disk utilization, to make sure the databases are correctly dimensioned. The curated dashboard also features write and read operations per second, concurrent connections and database state. Check Google Cloud SQL monitoring integration for details.
  • Google BigQuery is now available. Our curated dashboard helps keep track of query execution time, the number of bytes stored in the datasets, and the number of bytes uploaded to any table in the dataset that were billed. Check Google BigQuery monitoring integration for details.

Pages