You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/partner-solutions/new-relic/faq.yml
+25-25Lines changed: 25 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
### YamlMime:FAQ
2
2
metadata:
3
3
title: Azure Native New Relic Service frequently asked questions
4
-
description: Answers to common questions about using Azure Native New Relic Service
4
+
description: Answers to common questions about using Azure Native New Relic Service including getting started, management, and billing.
5
5
ms.topic: faq
6
6
ai-usage: ai-generated
7
7
ms.date: 12/17/2025
@@ -35,14 +35,14 @@ sections:
35
35
answer: |
36
36
To create an Azure Native New Relic Service resource, you need:
37
37
38
-
- An active Azure subscription with owner or contributor access
39
-
- A New Relic subscription (you can subscribe from the Azure portal during resource creation)
40
-
- The `NewRelic.Observability` resource provider registered in your Azure subscription
38
+
- An active Azure subscription with owner or contributor access.
39
+
- A New Relic subscription. You can subscribe from the Azure portal during resource creation.
40
+
- The `NewRelic.Observability` resource provider registered in your Azure subscription.
41
41
- question: How do I register the NewRelic.Observability resource provider?
42
42
answer: |
43
43
To register the resource provider using the Azure portal, follow the guidance in [Azure resource providers and types](/azure/azure-resource-manager/management/resource-providers-and-types).
44
44
45
-
Alternatively, you can register it from the command line by running: `az provider register --namespace NewRelic.Observability --subscription <subscription-id>`
45
+
Alternatively, you can register it from the command line by running: `az provider register --namespace NewRelic.Observability --subscription <subscription-id>`.
46
46
- question: Can I link an existing New Relic resource to Azure?
47
47
answer: |
48
48
Yes. If you already created New Relic resources outside of Azure, you can link them to your Azure subscription. During resource creation, select the **Create** button under *Link an existing New Relic resource* to associate existing New Relic accounts with your Azure Native New Relic Service resource.
@@ -53,13 +53,13 @@ sections:
53
53
answer: |
54
54
When using Azure Native New Relic Service, you receive a single bill for all resources you consume on Azure, including New Relic. An Azure Marketplace SaaS resource is created automatically based on the plan you select during resource creation. This resource is used for billing purposes.
55
55
56
-
Note: If you created your New Relic organization directly from the New Relic portal, the Azure Marketplace SaaS resource doesn't exist, and New Relic manages your billing separately.
56
+
Note: If you created your New Relic organization directly from the New Relic portal, Azure Marketplace SaaS resource doesn't exist, and New Relic manages your billing separately.
57
57
- question: What billing plans are available?
58
58
answer: |
59
59
Azure Native New Relic Service offers multiple billing plans that you can select during resource creation. You can change your billing plan after creation by selecting the **Change plan** link in the resource management portal.
60
60
- question: Do I need to subscribe to New Relic separately?
61
61
answer: |
62
-
You must have a New Relic subscription to use Azure Native New Relic Service. You can subscribe directly from the Azure portal during the resource creation process, or subscribe beforehand through the Azure Marketplace.
62
+
You must have a New Relic subscription to use Azure Native New Relic Service. You can subscribe directly from the Azure portal during the resource creation process, or subscribe beforehand through Azure Marketplace.
63
63
- question: What happens if my Azure subscription is suspended or deleted?
64
64
answer: |
65
65
If your Azure subscription is suspended or deleted due to payment-related issues, resource monitoring in New Relic automatically stops. To resume monitoring, use a different Azure subscription or add or update your payment method. For more information, see [Add, update, or delete a payment method](/azure/cost-management-billing/manage/change-credit-card).
@@ -86,7 +86,7 @@ sections:
86
86
You can also collect metrics for virtual machines and app services by installing the New Relic agent after creating the resource.
87
87
- question: Can I change my New Relic organization after creation?
88
88
answer: |
89
-
No. When you associate your Azure Native New Relic Service resource with a New Relic organization, that resource is billed to that organization's plan. If you need to change organizations, you may need to create a new resource.
89
+
No. When you associate your Azure Native New Relic Service resource with a New Relic organization, that resource is billed to that organization's plan. If you need to change organizations, you might need to create a new resource.
90
90
91
91
- name: Management and monitoring
92
92
questions:
@@ -111,10 +111,10 @@ sections:
111
111
The tag rules and logs you defined for the New Relic resource apply to all selected subscriptions.
112
112
- question: What should I do if I see duplicate data across subscriptions?
113
113
answer: |
114
-
If you have existing New Relic resources linked to the same New Relic organization, duplicate logs can result in unnecessary charges. To prevent this, delete redundant New Relic resources that are already linked to the account. We recommend consolidating subscriptions into the same New Relic resource where possible.
114
+
If you have existing New Relic resources linked to the same New Relic organization, duplicate logs can result in unnecessary charges. To prevent this situation, delete redundant New Relic resources that are already linked to the account. We recommend consolidating subscriptions into the same New Relic resource where possible.
115
115
- question: Can I reconfigure metrics and logs rules after creation?
116
116
answer: |
117
-
Yes. To change the configuration rules for metrics and logs, select **New Relic account config** > **Metrics and logs** from the service menu. Note that it takes up to one hour for modifications to tag rules to reflect in the log flow.
117
+
Yes. To change the configuration rules for metrics and logs, select **New Relic account config** > **Metrics and logs** from the service menu. It takes up to one hour for modifications to tag rules to reflect in the log flow.
118
118
- question: How do I view which resources are sending data to New Relic?
119
119
answer: |
120
120
To see the list of resources sending metrics and logs to New Relic, select **New Relic account config** > **Monitored resources** from the service menu. You can filter by resource type, resource group name, region, and whether the resource is sending metrics and logs.
@@ -127,30 +127,30 @@ sections:
127
127
128
128
- Virtual machines
129
129
- Virtual Machine Scale Sets
130
-
- App Services (Windows-based only; Linux App Services aren't supported)
130
+
- App Services (Windows-based only. Linux App Services isn't supported.)
131
131
132
132
Note: Function Apps aren't supported at this time.
133
133
- question: How do I install the New Relic agent?
134
134
answer: |
135
135
To install the New Relic agent:
136
136
137
-
1. Navigate to **New Relic account config** and select the resource type (**Virtual Machines**, **Virtual Machine Scale Sets**, or **App Services**)
138
-
2. Select the resources where you want to install the agent
139
-
3. Select **Install Extension** from the command bar
137
+
1. Navigate to **New Relic account config** and select the resource type: **Virtual Machines**, **Virtual Machine Scale Sets**, or **App Services**.
138
+
2. Select the resources where you want to install the agent.
139
+
3. Select **Install Extension** from the command bar.
140
140
141
141
Note: The agent can only be installed on running resources. Stopped virtual machines can't have the agent installed.
142
142
- question: Why can't I install an agent on my virtual machine?
143
143
answer: |
144
-
The New Relic agent can only be installed on virtual machines that are currently running. If your virtual machine is stopped, the install option will be disabled. Start the virtual machine first, then install the agent.
144
+
The New Relic agent can only be installed on virtual machines that are currently running. If your virtual machine is stopped, the install option is disabled. Start the virtual machine first, then install the agent.
145
145
- question: Can I uninstall the New Relic agent?
146
146
answer: |
147
-
Yes. You can uninstall the New Relic agent extension by selecting resources that have the agent installed and selecting **Uninstall Extension** from the command bar. Note that only resources with the agent currently installed can be selected for uninstallation.
147
+
Yes. You can uninstall the New Relic agent extension by selecting resources that have the agent installed and selecting **Uninstall Extension** from the command bar. Only resources with the agent currently installed can be selected for uninstallation.
148
148
- question: What does "Agent status Partially Installed" mean for Virtual Machine Scale Sets?
149
149
answer: |
150
-
This status appears when you have Virtual Machine Scale Sets with manual upgrade policy where preexisting instances didn't receive the extension automatically. To resolve this, manually install the New Relic agent for each preexisting virtual machine.
150
+
This status appears when you have Virtual Machine Scale Sets with manual upgrade policy where preexisting instances didn't receive the extension automatically. To resolve this situation, manually install the New Relic agent for each preexisting virtual machine.
151
151
- question: What is the difference between Web Apps and Function Apps?
152
152
answer: |
153
-
Azure Native New Relic Service supports Web App Services only. Function Apps aren't supported at this time. Additionally, extensions are only supported for App Services running on Windows operating systems; Linux App Services aren't displayed.
153
+
Azure Native New Relic Service supports Web App Services only. Function Apps aren't supported at this time. Additionally, extensions are only supported for App Services running on Windows operating systems; Linux App Services isn't displayed.
154
154
155
155
- name: Troubleshooting
156
156
questions:
@@ -161,24 +161,24 @@ sections:
161
161
answer: |
162
162
Resource monitoring is enabled through the ingest API key created during resource setup. If monitoring stopped:
163
163
164
-
- Check that the ingest API key hasn't been revoked from the New Relic portal (revoking it disrupts all monitoring)
165
-
- Verify your Azure subscription is active and not suspended due to payment issues
166
-
- Contact New Relic support if the issue persists
164
+
- Check that the ingest API key hasn't been revoked from the New Relic portal, because revoking it disrupts all monitoring.
165
+
- Verify your Azure subscription is active and not suspended due to payment issues.
166
+
- Contact New Relic support if the issue persists.
167
167
- question: Why are diagnostic settings still active after I disabled the New Relic resource?
168
168
answer: |
169
-
If diagnostic settings remain active after disabling the New Relic resource or applying tag rules, a delete lock may be applied to the resources or resource group. Delete locks prevent cleanup of diagnostic settings. Remove the lock from the resource or resource group to allow cleanup. If the lock is removed after the resource is deleted, you'll need to manually clean up the diagnostic settings to stop log forwarding.
169
+
If diagnostic settings remain active after disabling the New Relic resource or applying tag rules, a delete lock might be applied to the resources or resource group. Delete locks prevent cleanup of diagnostic settings. Remove the lock from the resource or resource group to allow cleanup. If the lock is removed after the resource is deleted, you'll need to manually clean up the diagnostic settings to stop log forwarding.
170
170
- question: Why are logs still being forwarded after I deleted the New Relic resource?
171
171
answer: |
172
-
If logs continue after deletion, a resource lock may be present on monitored Azure resources. Log forwarding will stop after 24 hours for locked resources. To stop forwarding immediately, remove the resource locks.
172
+
If logs continue after deletion, a resource lock might be present on monitored Azure resources. Log forwarding will stop after 24 hours for locked resources. To stop forwarding immediately, remove the resource locks.
173
173
- question: How long does it take for tag rule changes to take effect?
174
174
answer: |
175
175
It takes up to one hour for any modifications to tag rules to reflect in the log flow. For example, if you add a new resource to tag rules, it would take about one hour for log forwarding to start for that resource.
176
176
- question: How do I get support for Azure Native New Relic Service?
- Request support in the Azure portal: Select **Support + Troubleshooting** from the service menu, then choose the link to [log a support request in the New Relic portal](https://support.newrelic.com/)
- Request support in the Azure portal: Select **Support + Troubleshooting** from the service menu, then choose the link to [log a support request in the New Relic portal](https://support.newrelic.com/).
0 commit comments