Skip to content

Commit 10e5bb4

Browse files
Merge pull request #9746 from v-albemi/new-relic-troubleshoot
AB#8053: New Relic troubleshooting articles
2 parents 3c523dd + dddc989 commit 10e5bb4

File tree

4 files changed

+132
-2
lines changed

4 files changed

+132
-2
lines changed

support/azure/partner-solutions/index.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,5 +63,9 @@ landingContent:
6363
linkLists:
6464
- linkListType: how-to-guide
6565
links:
66+
- text: Can't install or uninstall the agent on a VM
67+
url: new-relic/install-uninstall-extension-vm.md
6668
- text: Update ingestion key after rotation
6769
url: ingestion-key-rotation-log-flow.md
70+
- text: Resource monitoring stopped working
71+
url: new-relic/resource-monitoring-troubleshoot.md
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Can't Install or Uninstall the Agent on a Virtual Machine
3+
description: Resolve problems with installing or uninstalling the New Relic agent on a virtual machine.
4+
author: shijojoy
5+
ms.author: jarrettr
6+
ms.reviewer: v-ryanberg
7+
ms.service: partner-services
8+
ms.topic: troubleshooting-problem-resolution
9+
ms.custom: New Relic troubleshooting
10+
ms.date: 09/18/2025
11+
ai-usage: ai-assisted
12+
13+
#customer intent: As an Azure administrator or user, I want to resolve problems with installing or uninstalling the New Relic agent on virtual machines.
14+
15+
---
16+
17+
# Can't install or uninstall the agent on a virtual machine
18+
19+
This article explains how to resolve problems with installing or uninstalling the New Relic agent on a virtual machine (VM). Specifically, it describes what to do if you select VMs and the **Install Extension** or **Uninstall Extension** button is unavailable.
20+
21+
## Prerequisites
22+
23+
- An Azure account with permissions to manage VM extensions (Contributor or Owner on the subscription or resource group, or a role with explicit extension management permissions).
24+
- The target VMs must be visible in the Azure portal on the **Virtual machines** page.
25+
26+
## Symptoms
27+
28+
- On the **Virtual Machines** page of the New Relic resource, the **Install Extension** button is unavailable (dimmed) after you select one or more VMs.
29+
- On the **Virtual Machines** page of the New Relic resource, the **Uninstall Extension** button is unavailable (dimmed) after you select one or more VMs.
30+
31+
## Cause
32+
33+
The portal enables the **Install Extension** or **Uninstall Extension** button only when the entire selection of VMs matches the required state for that action:
34+
35+
- **Install Extension** is enabled only when none of the selected VMs has the New Relic agent installed.
36+
- **Uninstall Extension** is enabled only when every selected VM already has the New Relic agent installed.
37+
38+
The Azure portal displays the agent/extension state in the **Agent status** column:
39+
40+
- VMs on which the New Relic agent is installed show **Running** or **Shutdown**.
41+
- VMs on which the New Relic agent isn't installed show **Not Installed**.
42+
43+
If your selection includes VMs in different states (some that have the agent and some that don't), neither **Install Extension** nor **Uninstall Extension** will be enabled.
44+
45+
## Solution
46+
47+
1. In the Azure portal, go to the **Virtual Machines** page of the New Relic resource.
48+
1. To install the New Relic agent:
49+
1. Select only VMs that show an **Agent status** of **Not Installed**.
50+
1. Deselect any VMs that show a status of **Running** or **Shutdown**. (These VMs already have the agent.)
51+
1. Confirm that the **Install Extension** button is active and then proceed.
52+
1. To uninstall the New Relic agent:
53+
1. Select only VMs that show an **Agent status** of **Running** or **Shutdown**. (These VMs have the agent installed.)
54+
1. Deselect any VMs that show a status of **Not Installed**.
55+
1. Confirm that the **Uninstall Extension** button is active and then proceed.
56+
57+
## Related content
58+
59+
- [Manage extensions on Azure virtual machines](/azure/virtual-machines/extensions/overview)
60+
- [Troubleshoot VM Agent issues](../../virtual-machines/windows/windows-azure-guest-agent.md)
61+
- [Introduction to the Azure Native New Relic Service](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/)
62+
63+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
64+
65+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Resource Monitoring Stopped Working
3+
description: Troubleshoot situations in which New Relic stops receiving logs or metrics from Azure resources.
4+
author: shijojoy
5+
ms.author: jarrettr
6+
ms.reviewer: v-ryanberg
7+
ms.service: partner-services
8+
ms.topic: troubleshooting-general
9+
ms.custom: New Relic troubleshooting
10+
ms.date: 09/19/2025
11+
ai-usage: ai-assisted
12+
13+
#customer intent: As an Azure administrator or user, I want to troubleshoot situations in which New Relic monitoring stops working.
14+
15+
---
16+
17+
# Resource monitoring stopped working
18+
19+
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.
20+
21+
## Prerequisites
22+
23+
- Access to the New Relic account that owns the ingest API key (API key admin or owner).
24+
- Access to the Azure subscription and resource group that contain the affected resources (Reader to view, Contributor/Owner to remediate or change billing).
25+
26+
## Causes and solutions
27+
28+
### Cause: Ingest API key is revoked
29+
30+
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.
31+
32+
#### Solution
33+
34+
- If the API key is revoked, contact [New Relic support](https://support.newrelic.com/).
35+
36+
### Cause: Azure subscription suspended or deleted
37+
38+
If your Azure subscription is suspended or deleted for payment-related issues, resource monitoring in New Relic automatically stops.
39+
40+
#### Solution
41+
42+
- 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](/azure/cost-management-billing/manage/change-credit-card).
43+
44+
### Cause: New Relic service issues
45+
46+
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.
47+
48+
#### Solution
49+
50+
If your Azure subscription and resource are working correctly but the New Relic portal shows problems with monitoring data, contact [New Relic support](https://support.newrelic.com/).
51+
52+
## Related content
53+
54+
- [Add, update, or delete a payment method](/azure/cost-management-billing/manage/change-credit-card)
55+
- [New Relic support](https://support.newrelic.com/)
56+
57+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
58+
59+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/partner-solutions/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ items:
4949
href: informatica/resource-creation.md
5050
- name: New Relic
5151
items:
52+
- name: Can't install or uninstall the agent on a VM
53+
href: new-relic/install-uninstall-extension-vm.md
5254
- name: Diagnostic settings manual update
5355
href: diagnostic-settings-manual-update.md
5456
- name: Diagnostic settings not created
@@ -59,5 +61,5 @@ items:
5961
href: log-forwarding-persists.md
6062
- name: Log limitations
6163
href: log-limitations.md
62-
63-
64+
- name: Resource monitoring stopped working
65+
href: new-relic/resource-monitoring-troubleshoot.md

0 commit comments

Comments
 (0)