Cloud integrations release notesRSS

Update

• We've released an update to the AWS CloudFormation template for our Metric Streams integration. This update resolves a critical issue that could prevent the stack from being updated and use modern AWS Lambda python runtimes.

• To apply the fix to your existing integration, please follow the steps below to update your CloudFormation stack:

  1. Navigate to CloudFormation: Log in to your AWS Management Console and go to the CloudFormation service.

  2. Select Your Stack: Find and select your New Relic Metric Streams stack (it's often named NewRelic-Metric-Streams-*), then click Update Stack dropdown. From the options, select Make a direct update. For more information, see the AWS documentation on directly updating stacks.

  3. Replace Template: On the update screen, you must select Replace current template.

     NOTE: Do not use the "Use existing template" option, as it will not apply the necessary fixes.

  4. Provide the New Template URL: Under the Specify template section, choose the Amazon S3 URL option and paste the following link:

     https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/newrelic-cloudformation-mstreams.yml

  5. Confirm and Update: Click Next through the parameter and stack options pages. On the final review page, scroll to the bottom, check the box to acknowledge that AWS CloudFormation might create IAM resources, and click Update stack.

  You can monitor the progress in the Events tab. The update is complete when the stack status changes to UPDATE_COMPLETE.

アップデート

• メトリクス ストリーム統合用のAWS CloudFormation テンプレートの更新をリリースしました。 この更新により、スタックが更新されず、最新の AWS Lambda Python ランタイムを使用できなくなる可能性がある重大な問題が解決されます。

• 既存の統合に修正を適用するには、以下の手順に従って CloudFormation スタックを更新してください。

  1. CloudFormation に移動します。AWS マネジメントコンソールにログインし、 CloudFormationサービスに移動します。

  2. スタックを選択: New Relicメトリクス ストリーム スタック (通常はNewRelic-Metric-Streams-*という名前が付けられます) を見つけて選択し、 Update Stack [スタックの更新]ドロップダウンをクリックします。 オプションから、 Make a direct update [直接更新する] を選択します。詳細については、 スタックの直接更新に関する AWS ドキュメントを参照してください。

  3. テンプレートの置き換え: 更新画面で、現在のテンプレートの置き換えを選択するReplace current template [必要があります]。

  注意: 必要な修正が適用されないため、"Use existing template" [既存のテンプレートを使用する] オプションは使用しないでください。

  4. 新しいテンプレートの URL を指定します。テンプレートの指定セクションで、 Amazon S3 URLオプションを選択し、次のリンクを貼り付けます。

  https://nr-downloads-main.s3.amazonaws.com/cloud_integrations/aws/cloudformation/newrelic-cloudformation-mstreams.yml

  5. 確認して更新: [被害] および [スタック] オプション ページでNext[次へ] をクリックします。 最終確認ページで一番下までスクロールし、 AWS CloudFormation によって IAM リソースが作成される可能性があることを認めるボックスをオンにして、 Update stack[スタックの更新]をクリックします。

  Events [イベント] タブで進行状況を監視できます。 スタックのステータスがUPDATE_COMPLETEに変わると更新が完了します。

Agentless monitoring for EC2, Azure VM, and standardized entity creation across EC2, Azure VMs, and GCP CE is now available.

What's new

We updated our cloud host monitoring capabilities to help you monitor your Amazon EC2, Azure VM, and GCP CE instances more effectively. You'll now have access to:

• Enhanced visibility into your Amazon EC2 and Azure VM infrastructure without the need for complex setup or configuration.
• Simplified set-up that eliminates manual agent installations and configuration.
• For a cloud resource (EC2, Azure VM, GCP CE) same entity is created when they are instrumented by both agents or as well as in agentless mode (API Polling - AWS/Azure/GCP, Cloudwatch Metric Streams integration, Azure Monitor integration)

New Relic can detect your cloud host instances, create entities for them, and provide comprehensive insight into each host's performance, resource utilization, and health.

Fixes to Cloud Integrations API Validations

We're updating how NerdGraph handles certain requests for the cloud namespace:

• The validations for boolean fields have been updated. From now on, null values will be rejected for these fields.
• The inventory polling interval and metrics polling interval integer fields have been updated as well. Going forward, these fields will no longer accept null values.
• The tagKey parameter under GCP and AWS integrations will no longer accept empty strings as value.

These updates are a bugfix that prevent you from using these values, which in some cases are broken or functionally confusing.

Please ensure that you're providing valid values for these fields in your requests.

To get more information on how to use cloud integration APIs, please see the Configure cloud integrations NerdGraph tutorial.

New

• The Azure Monitor Integration is now available! This new integration enables customers to get all metrics available from Azure Monitor. Check out the documentation for more information.

New

• Azure Monitor metrics integration is now on Public Preview. This new integration allows to get all metrics available from Azure Monitor. Please refer to the documentation for details.

New

• Azure PostgreSQL and MyQL flexible servers integrations are now available. Check PostgreSQL flexible monitoring integration and MySQL flexible monitoring integration for details.

New

• AlloyDB for PostgreSQL integration is now available. New Relic collects metrics for AlloyDB clusters, databases and instances. Check AlloyDB monitoring integration for details.

Updated

As previously announced, we're ending support for Inventory data pushed from our Cloud Integrations (AWS, Azure, GCP).

What is changing?

Inventory data is currently collected on many AWS, Azure, and GCP integrations. It represents static configuration data or resource metadata. Information from hosts or on-host integrations in Inventory is not affected by this change.

What is Inventory?

Inventory data is information about the state and configuration of a service, e.g. service settings. Data appears in the Inventory page and some integration dashboards in the original infrastructure experience. Changes to inventory data generate New Relic InfrastructureEvent events that can be queried and alerted on.

Capabilities that will no longer be available

• When browsing to Infrastructure > Inventory, any source from aws/*, azure/* or gcp/* will no longer be available.
• Built-in dashboards available in Infrastructure > AWS | Azure | GCP | GovCloud that contain inventory or infrastructure events widgets will no longer display data. These dashboards are planned to be migrated as standard New Relic dashboards enabling all the new capabilities (edit, sharing, new visualizations, and more) which are not available in the original dashboard experience for infrastructure monitoring.
• Queries using aws, azure or gcp sources from InfrastructureEvent will no longer report data.

Why is this capability being deprecated?

• Customers find more value in Host Inventory, which is not being deprecated, but less value in Cloud Integrations.

Alternatives

• Most of the attributes available as Inventory in the polling integrations are also available as metric metadata or tags, so you can query for this information.
• A limited set of integrations also published the same information available in Inventory as standard New Relic Events. In example, the AWS Health integration.

How does this affect AWS CloudWatch metric streams and future integrations for Azure & GCP?

• Inventory isn't available in AWS CloudWatch metric stream, so there's no impact on this capability.
• New integrations for Azure and GCP will be focused on MELT telemetry: Metrics, Events, Logs & Traces, with special focus on Metrics.

Feedback

After this feature is deprecated, if you encounter any issues, you can get help by following these steps in the UI:

1. Log in to your New Relic account.
2. Visit our comprehensive Help Center. It contains a wealth of information and resources.
3. If you need further assistance, click Create a Support Case and our team will be happy to assist you.