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 Management Console에 로그인하고 CloudFormation 서비스로 이동합니다.

  2. 그리드 선택: 뉴렐릭 지표 Streams 그리드(종종 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.