Edit

Share via

Resource monitoring stopped working

This article helps you troubleshoot situations in which New Relic stops receiving telemetry (logs, metrics, or events) from Azure resources like virtual machines (VMs) and app services.

Prerequisites

  • Access to the New Relic account that owns the ingest API key (API key admin or owner).
  • Access to the Azure subscription and resource group that contain the affected resources (Reader to view, Contributor/Owner to remediate or change billing).

Causes and solutions

Cause: Ingest API key is revoked

Resource monitoring in New Relic is enabled through the ingest API key, which you set up at the time of resource creation. Revoking the ingest API key from the New Relic portal disrupts monitoring of logs and metrics for all resources, including virtual machines and app services. You shouldn't revoke the ingest API key.

Solution

Cause: Azure subscription suspended or deleted

If your Azure subscription is suspended or deleted for payment-related issues, resource monitoring in New Relic automatically stops.

Solution

  • If the subscription is suspended or deleted for payment-related reasons, either update the payment method or move resources to an active subscription. For more information, see Add, update, or delete a payment method.

Cause: New Relic service issues

New Relic manages the APIs for creating and managing resources, and for the storage and processing of telemetry data. The New Relic APIs might be on or outside of Azure. Some issues can originate outside of Azure.

Solution

If your Azure subscription and resource are working correctly but the New Relic portal shows problems with monitoring data, contact New Relic support.

Related content

Contact us for help

If you have questions, you can ask Azure community support. You can also submit product feedback to Azure feedback community.

Third-party contact disclaimer

Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

  • Last updated on