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
If those options don't solve the problem, contact [Dynatrace support](https://support.dynatrace.com/).
19
19
20
-
###Unable to create Dynatrace resource
20
+
## Unable to create Dynatrace resource
21
21
22
22
- To set up the Azure Native Dynatrace Service, you must have **Owner** or **Contributor** access on the Azure subscription. Ensure you have the appropriate access before starting the setup.
23
23
24
24
- Create fails because Last Name is empty. The issue happens when the user info in Microsoft Entra ID is incomplete and doesn't contain Last Name. Contact your Azure tenant's global administrator to rectify the issue and try again.
25
25
26
-
###Logs not being emitted or limit reached issue
26
+
## Logs not being emitted or limit reached issue
27
27
28
28
- Resource doesn't support sending logs. Only resource types with monitoring log categories can be configured to send logs. For more information, see [supported categories](../../azure-monitor/essentials/resource-logs-categories.md).
29
29
30
30
- Limit of five diagnostic settings reached. This displays the message of Limit reached against the resource. Each Azure resource can have a maximum of five diagnostic settings. For more information, see [diagnostic settings](../../azure-monitor/essentials/diagnostic-settings.md?tabs=portal) You can go ahead and remove the other destinations to make sure each resource is sending data to at max five destinations.
31
31
32
32
- Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings.
33
33
34
-
###Single sign-on errors
34
+
## Single sign-on errors
35
35
36
36
-**Single sign-on configuration indicates lack of permissions**
37
37
- Occurs when the user that is trying to configure single sign-on doesn't have Manage users permissions for the Dynatrace account. For a description of how to configure this permission, see [here](https://www.dynatrace.com/support/help/shortlink/azure-native-integration#setup).
@@ -41,15 +41,15 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
41
41
-**App not showing in Single sign-on settings page**
42
42
- First, search for application ID. If no result is shown, check the SAML settings of the app. The grid only shows apps with correct SAML settings.
43
43
44
-
###Metrics checkbox disabled
44
+
## Metrics checkbox disabled
45
45
46
46
- To collect metrics, you must have owner permission on the subscription. If you're a contributor, refer to the contributor guide mentioned in [Configure metrics and logs](dynatrace-create.md#configure-metrics-and-logs).
47
47
48
-
###Diagnostic settings are active even after disabling the Dynatrace resource or applying necessary tag rules
48
+
## Diagnostic settings are active even after disabling the Dynatrace resource or applying necessary tag rules
49
49
50
50
If logs are being emitted and diagnostic settings remain active on monitored resources even after the Dynatrace resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this, remove the delete lock from the resource or the resource group. If the lock is removed after the Dynatrace resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
51
51
52
-
###Free trial errors
52
+
## Free trial errors
53
53
54
54
-**Unable to create another free trial resource on Azure**
55
55
- During free trials, Dynatrace accounts can only have one environment. You can therefore create only one Dynatrace resource during the trial period.
To set up Azure Native New Relic Service, you must have owner access on the Azure subscription. Ensure that you have the appropriate access before you start the setup.
21
21
22
22
To find the New Relic offering on Azure and set up the service, you must first register the `NewRelic.Observability` resource provider in your Azure subscription. To register the resource provider by using the Azure portal, follow the guidance in [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
23
23
To register the resource provider from a command line, enter `az provider register --namespace NewRelic.Observability --subscription <subscription-id>`.
24
24
25
-
###Logs aren't being sent to New Relic
25
+
## Logs aren't being sent to New Relic
26
26
27
27
Only resource types in [supported categories](../../azure-monitor/essentials/resource-logs-categories.md) send logs to New Relic through the integration. To check whether the resource is set up to send logs to New Relic, go to the [Azure diagnostic settings](/azure/azure-monitor/platform/diagnostic-settings) for that resource. Then, verify that there's a New Relic diagnostic setting.
28
28
29
-
###You can't install or uninstall an extension on a virtual machine
29
+
## You can't install or uninstall an extension on a virtual machine
30
30
31
31
Only virtual machines without the New Relic agent installed should be selected together to install the extension. Deselect any virtual machines that already have the New Relic agent installed, so that **Install Extension** is active. The **Agent Status** column shows the status **Running** or **Shutdown** for any virtual machines that already have the New Relic agent installed.
32
32
33
33
Only virtual machines that currently have the New Relic agent installed should be selected together to uninstall the extension. Deselect any virtual machines that don't already have the New Relic agent installed, so that **Uninstall Extension** is active. The **Agent Status** column shows the status **Not Installed** for any virtual machines that don't already have the New Relic agent installed.
34
34
35
-
###Resource monitoring stopped working
35
+
## Resource monitoring stopped working
36
36
37
37
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. If the API key is already revoked, contact New Relic support.
38
38
39
39
If your Azure subscription is suspended or deleted because of payment-related issues, resource monitoring in New Relic automatically stops. Use a different Azure subscription. Or, add or update the credit card or payment method for the subscription. For more information, see [Add, update, or delete a payment method](../../cost-management-billing/manage/change-credit-card.md).
40
40
41
41
New Relic manages the APIs for creating and managing resources, and for the storage and processing of customer telemetry data. The New Relic APIs might be on or outside Azure. If your Azure subscription and resource are working correctly but the New Relic portal shows problems with monitoring data, contact New Relic support.
42
42
43
-
###Diagnostic settings are active even after disabling the New Relic resource or applying necessary tag rules
43
+
## Diagnostic settings are active even after disabling the New Relic resource or applying necessary tag rules
44
44
45
45
If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
0 commit comments