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
title: Get support for Azure Native Dynatrace Service
3
+
description: This article shows you how to get support when using Azure Native Dynatrace Service on the Azure Cloud.
4
+
ms.topic: how-to
5
+
ms.date: 07/03/2024
6
+
7
+
#customer intent: As an implementer of Dynatrace on the Azure Cloud, I want to file a support request so that I can get unblocked.
8
+
---
9
+
10
+
# Get support for Azure Native Dynatrace Service
11
+
12
+
In this article, you learn how to contact support when working with an Azure Native Dynatrace Service resource. Before contacting support, see [Fix common errors](dynatrace-troubleshoot.md).
13
+
14
+
## How to contact support
15
+
16
+
1. In the Azure portal, go to your Dynatrace resource.
17
+
18
+
1. In Resource menu, under **Support + troubleshooting**, select **New Support Request**.
19
+
20
+
1. Select the link to go to the [Dynatrace support website](https://support.dynatrace.com/) and raise a request.
21
+
22
+
:::image type="content" source="media/dynatrace-troubleshoot/dynatrace-support.png" alt-text="Screenshot showing new support request selected in resource menu.":::
23
+
24
+
## Related content
25
+
26
+
- Learn about [managing your instance](dynatrace-how-to-manage.md) of Dynatrace.
27
+
- Get started with Azure Native Dynatrace Service on
Copy file name to clipboardExpand all lines: articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md
+9-19Lines changed: 9 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,45 +3,35 @@ title: Troubleshooting Azure Native Dynatrace Service
3
3
description: This article provides information about troubleshooting Dynatrace for Azure
4
4
5
5
ms.topic: conceptual
6
-
ms.date: 02/02/2023
6
+
ms.date: 06/20/2024
7
7
8
8
---
9
9
10
10
# Troubleshoot Azure Native Dynatrace Service
11
11
12
-
In this article, you learn how to contact support when working with an Azure Native Dynatrace Service resource. Before contacting support, see [Fix common errors](#fix-common-errors).
13
-
14
-
## Contact support
15
-
16
-
To contact support about the Azure Native Dynatrace Service, select **New Support request** in the left pane. Select the link to the Dynatrace support website.
17
-
18
-
:::image type="content" source="media/dynatrace-troubleshoot/dynatrace-support.png" alt-text="Screenshot showing new support request selected in resource menu.":::
19
-
20
-
## Fix common errors
21
-
22
12
This document contains information about troubleshooting your solutions that use Dynatrace.
If those options don't solve the problem, contact [Dynatrace support](https://support.dynatrace.com/).
29
19
30
-
###Unable to create Dynatrace resource
20
+
## Unable to create Dynatrace resource
31
21
32
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.
33
23
34
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.
35
25
36
-
###Logs not being emitted or limit reached issue
26
+
## Logs not being emitted or limit reached issue
37
27
38
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).
39
29
40
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.
41
31
42
32
- Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings.
43
33
44
-
###Single sign-on errors
34
+
## Single sign-on errors
45
35
46
36
-**Single sign-on configuration indicates lack of permissions**
47
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).
@@ -51,15 +41,15 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
51
41
-**App not showing in Single sign-on settings page**
52
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.
53
43
54
-
###Metrics checkbox disabled
44
+
## Metrics checkbox disabled
55
45
56
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).
57
47
58
-
###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
59
49
60
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.
61
51
62
-
###Free trial errors
52
+
## Free trial errors
63
53
64
54
-**Unable to create another free trial resource on Azure**
65
55
- During free trials, Dynatrace accounts can only have one environment. You can therefore create only one Dynatrace resource during the trial period.
title: Get support for Azure Native New Relic Service
3
+
description: This article shows you how to get support when using Azure Native New Relic Service with the Azure Cloud.
4
+
ms.topic: how-to
5
+
6
+
ms.date: 07/03/2024
7
+
#customer intent: As an implementer of New Relic on the Azure Cloud, I want to file a support request so that I can get unblocked.
8
+
---
9
+
10
+
# Get support for Azure Native New Relic Service
11
+
12
+
In this article, you learn how to contact support when working with an Azure Native New Relic Service resource. Before contacting support, see [Fix common errors](new-relic-troubleshoot.md).
13
+
14
+
## How to contact support
15
+
16
+
1. In the Azure portal, go to the resource.
17
+
1. On the left pane, under **Support + troubleshooting**, select **New Support Request**.
18
+
1. Select the link to go to the [New Relic support website](https://support.newrelic.com/) and raise a request.
19
+
20
+
:::image type="content" source="media/new-relic-troubleshoot/new-relic-support.png" alt-text="Screenshot that shows the pane for a New Relic support request.":::
21
+
22
+
## Related content
23
+
24
+
-[Manage Azure Native New Relic Service](new-relic-how-to-manage.md)
25
+
- Get started with Azure Native New Relic Service on
Copy file name to clipboardExpand all lines: articles/partner-solutions/new-relic/new-relic-troubleshoot.md
+6-16Lines changed: 6 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,46 +11,36 @@ ms.date: 01/16/2023
11
11
12
12
This article describes how to fix common problems when you're working with Azure Native New Relic Service resources.
13
13
14
-
Try the troubleshooting information in this article first. If that doesn't work, contact New Relic support:
15
-
16
-
1. In the Azure portal, go to the resource.
17
-
1. On the left pane, under **Support + troubleshooting**, select **New Support Request**.
18
-
1. Select the link to go to the [New Relic support website](https://support.newrelic.com/) and raise a request.
19
-
20
-
:::image type="content" source="media/new-relic-troubleshoot/new-relic-support.png" alt-text="Screenshot that shows the pane for a New Relic support request.":::
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.
31
21
32
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).
33
23
To register the resource provider from a command line, enter `az provider register --namespace NewRelic.Observability --subscription <subscription-id>`.
34
24
35
-
###Logs aren't being sent to New Relic
25
+
## Logs aren't being sent to New Relic
36
26
37
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.
38
28
39
-
###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
40
30
41
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.
42
32
43
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.
44
34
45
-
###Resource monitoring stopped working
35
+
## Resource monitoring stopped working
46
36
47
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.
48
38
49
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).
50
40
51
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.
52
42
53
-
###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
54
44
55
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