Skip to content

Commit b8f1bbe

Browse files
Merge pull request #9753 from v-albemi/datadog-troubleshooting
AB#9127: Datadog troubleshooting articles
2 parents d162c71 + dbeedca commit b8f1bbe

4 files changed

Lines changed: 144 additions & 11 deletions

File tree

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Troubleshoot Default API Key Problems in Datadog
3+
description: Resolve Datadog agent installation failures caused by a missing default API key, or change an incorrect default API key.
4+
author: agrimayadav
5+
ms.author: jarrettr
6+
ms.service: partner-services
7+
ms.topic: troubleshooting-general
8+
ms.date: 09/22/2025
9+
ai-usage: ai-assisted
10+
11+
# customer intent: As an Azure administrator or user, I want to resolve an installation failure that's caused by a missing default API key, or I want to change a default API key.
12+
13+
---
14+
15+
# Datadaog agent installation fails, or default API key is incorrect
16+
17+
## Summary
18+
19+
The Azure Datadog integration enables you to install a Datadog agent on a virtual machine or app service. This article helps you troubleshoot Datadog agent installation failures that are caused by a missing default API key. It also describes how to change the default key.
20+
21+
## Prerequisites
22+
23+
- Access to the [Azure portal](https://portal.azure.com) with permissions to view or configure the Datadog integration and to restart virutal machines (VMs) or app services if required.
24+
25+
## Problems and solutions
26+
27+
### Problem: Datadog installation fails
28+
29+
If a default API key isn't selected, the Datadog agent installation fails.
30+
31+
#### Solution
32+
33+
1. In the Azure portal, go to the Datadog resource.
34+
1. Select **Settings** > **Keys**.
35+
1. In **API Keys**, change the default key.
36+
1. Try again to install the agent.
37+
38+
### Problem: Incorrect API key configured on the resource
39+
40+
The API key for the resource is incorrect.
41+
42+
#### Solution
43+
44+
1. In the Azure portal, go to the Datadog resource.
45+
1. Select **Settings** > **Keys**.
46+
1. In **API Keys**, change the default key.
47+
1. Uninstall the Datadog agent and reinstall it.
48+
49+
## Related content
50+
51+
- [Datadog agent installation docs](https://docs.datadoghq.com/agent/)
52+
- [Datadog Azure integration documentation](https://docs.datadoghq.com/integrations/azure/)
53+
- [Manage extensions on Azure virtual machines](/azure/virtual-machines/extensions/overview)
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Metrics Not Being Emitted
3+
description: Resolve the problem in which Datadog doesn't receive metrics from Azure resources because of a missing or incorrect role assignment.
4+
author: agrimayadav
5+
ms.author: jarrettr
6+
ms.service: partner-services
7+
ms.topic: troubleshooting-problem-resolution
8+
ms.date: 09/19/2025
9+
ai-usage: ai-assisted
10+
11+
#customer intent: As an Azure administrator or user, I want to resolve an issue in which Datadog isn't emitting metrics.
12+
13+
---
14+
15+
# Metrics not being emitted
16+
17+
## Summary
18+
19+
This article helps you resolve when Datadog isn't receiving metrics from Azure resources because the Datadog resource identity doesn't have the required Monitoring Reader role assignment.
20+
21+
## Prerequisites
22+
23+
- Access to the [Azure portal](https://portal.azure.com) with permissions to view access control (IAM) for the target subscription (Reader) and to assign roles (Contributor/Owner) if you will remediate the problem.
24+
- The Datadog resource identity (managed identity or service principal) name or principal ID.
25+
26+
## Symptoms
27+
28+
- Metrics from Azure resources don't appear in the Datadog UI.
29+
- The Datadog resource doesn't show a **Monitoring Reader** role assignment in the subscription's IAM list.
30+
31+
## Cause
32+
33+
Datadog requires the **Monitoring Reader** role on the appropriate Azure subscription to collect platform metrics. If the Datadog resource identity isn't assigned this role, Datadog can't read metrics and they won't be emitted to Datadog.
34+
35+
## Solution
36+
37+
1. In the Azure portal, open the subscription that contains the resource.
38+
39+
1. Select **Access control (IAM)**.
40+
41+
1. On the **Role assignments** tab, search for the Datadog resource name.
42+
43+
1. If you don't find a Monitoring Reader assignment for the Datadog identity, complete these steps to add one:
44+
45+
1. Select **Add** > **Add role assignment**.
46+
47+
1. On the **Role** tab, select **Monitoring Reader**, and then select **Next**.
48+
49+
1. In **Assign access to**, select **Managed identity** or **Service principal** as appropriate.
50+
51+
1. Select the Datadog resource identity and then choose **Select**.
52+
53+
1. Wait a few minutes for role-based access control (RBAC) propagation, and then verify that Datadog is receiving metrics.
54+
55+
> [!warning]
56+
> If you remove the system managed identity or the Monitoring Reader role assignment, Datadog can't collect metrics from your Azure resources.
57+
58+
> [!Note]
59+
> Confirm that the Datadog identity is the one used by the Datadog integration (managed identity versus service principal). If you assign the role to the wrong principal, Datadog won't receive metrics.
60+
61+
## Resources
62+
63+
- [Azure role-based access control (RBAC)](/azure/role-based-access-control/)
64+
- [Assign Azure roles using the Azure CLI](/azure/role-based-access-control/role-assignments-cli)
65+
- [Datadog Azure integration documentation](https://docs.datadoghq.com/integrations/azure/)

support/azure/partner-solutions/index.yml

Lines changed: 22 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -62,22 +62,33 @@ landingContent:
6262
# Card
6363
- title: Astro
6464
linkLists:
65-
- linkListType: how-to-guide
66-
links:
67-
- text: Can't create Astro resources in Azure
68-
url: astro/resource-creation.md
69-
- text: Can't install Astro using a personal email
70-
url: astro/personal-email.md
71-
- text: Unable to use single sign-on in Astronomer portal
72-
url: astro/single-sign-on.md
65+
- linkListType: how-to-guide
66+
links:
67+
- text: Can't create Astro resources in Azure
68+
url: astro/resource-creation.md
69+
- text: Can't install Astro using a personal email
70+
url: astro/personal-email.md
71+
- text: Unable to use single sign-on in Astronomer portal
72+
url: astro/single-sign-on.md
7373

7474
# Card
75-
- title: Informatica
75+
- title: Datadog
7676
linkLists:
7777
- linkListType: how-to-guide
7878
links:
79-
- text: Issues creating Informatica resources in Azure
80-
url: informatica/resource-creation.md
79+
- text: Datadaog agent installation fails, or default API key is incorrect
80+
url: datadog/installation-fails.md
81+
- text: Metrics not being emitted
82+
url: datadog/metrics-not-emitted.md
83+
84+
# Card
85+
- title: Informatica
86+
linkLists:
87+
- linkListType: how-to-guide
88+
links:
89+
- text: Issues creating Informatica resources in Azure
90+
url: informatica/resource-creation.md
91+
8192

8293
# Card
8394
- title: Observability partners

support/azure/partner-solutions/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,8 @@ items:
3939
href: astro/single-sign-on.md
4040
- name: Datadog
4141
items:
42+
- name: Datadaog agent installation fails, or default API key is incorrect
43+
href: datadog/installation-fails.md
4244
- name: Diagnostic settings manual update
4345
href: diagnostic-settings-manual-update.md
4446
- name: Diagnostic settings not created
@@ -47,6 +49,8 @@ items:
4749
href: log-forwarding-persists.md
4850
- name: Log limitations
4951
href: log-limitations.md
52+
- name: Metrics not being emitted
53+
href: datadog/metrics-not-emitted.md
5054
- name: Dynatrace
5155
items:
5256
- name: AKS agent installation/uninstallation unavailable

0 commit comments

Comments
 (0)