Skip to content

Commit 8db51da

Browse files
committed
edits
1 parent 6694ff5 commit 8db51da

2 files changed

Lines changed: 4 additions & 2 deletions

File tree

support/azure/partner-solutions/datadog/metrics-not-emitted.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article helps you resolve the problem in which Datadog isn't receiving metr
1818

1919
## Prerequisites
2020

21-
- Access to the Azure portal with permissions to view access control (IAM) for the target subscription (Reader) and to assign roles (Contributor/Owner) if you will remediate.
21+
- Access to the Azure portal with permissions to view access control (IAM) for the target subscription (Reader) and to assign roles (Contributor/Owner) if you will remediate the problem.
2222
- The Datadog resource identity (managed identity or service principal) name or principal ID.
2323

2424
## Symptoms
@@ -48,7 +48,7 @@ Datadog requires the Monitoring Reader role on the appropriate Azure subscriptio
4848

4949
1. Select the Datadog resource identity and then click **Select**.
5050

51-
1. Wait a few minutes for RBAC propagation, and then verify that Datadog is recieving metrics.
51+
1. Wait a few minutes for RBAC propagation, and then verify that Datadog is receiving metrics.
5252

5353
> [!Note]
5454
> Confirm the Datadog identity is the one used by the Datadog integration (managed identity vs. service principal). If you assign the role to the wrong principal, Datadog won't receive metrics.

support/azure/partner-solutions/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ items:
1313
href: log-forwarding-persists.md
1414
- name: Log limitations
1515
href: log-limitations.md
16+
- name: Metrics not being emitted
17+
href: metrics-being-emitted.md
1618
- name: Dynatrace
1719
items:
1820
- name: Diagnostic settings manual update

0 commit comments

Comments
 (0)