Skip to content

Commit bfa1917

Browse files
committed
fixes
1 parent b25b0e0 commit bfa1917

File tree

3 files changed

+10
-9
lines changed

3 files changed

+10
-9
lines changed

articles/azure-monitor/containers/prometheus-remote-write-troubleshooting.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ ms.date: 4/18/2024
1313

1414
# Troubleshoot remote write
1515

16+
This article describes how to troubleshoot remote write in Azure Monitor Managed Service for Prometheus. For more information about remote write, see [Remote write in Azure Monitor Managed Service for Prometheus](./prometheus-remote-write.md).
1617

1718
## Supported versions
1819

articles/azure-monitor/essentials/prometheus-remote-write-virtual-machines.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article explains how to configure remote-write to send data from a self-man
2020

2121
Self-managed Prometheus can run on Azure and non-Azure environments. The following are authentication options for remote-write to Azure Monitor workspace based on the environment where Prometheus is running.
2222

23-
#### Azure managed Virtual Machines and Virtual Machine Scale Sets
23+
## Azure managed Virtual Machines and Virtual Machine Scale Sets
2424

2525
Use user-assigned managed identity authentication for services running self managed Prometheus in an Azure environment. Azure managed services include:
2626

@@ -31,7 +31,7 @@ Use user-assigned managed identity authentication for services running self mana
3131
To set up remote write for Azure managed resources, see [Remote-write using user-assigned managed identity](#remote-write-using-user-assigned-managed-identity-authentication).
3232

3333

34-
#### Virtual machines running on non-Azure environments.
34+
## Virtual machines running on non-Azure environments.
3535

3636
Onboarding to Azure Arc-enabled services, allows you to manage and configure non-Azure virtual machines in Azure. Once onboarded, configure [Remote-write using user-assigned managed identity](#remote-write-using-user-assigned-managed-identity-authentication) authentication. For more Information on onboarding Virtual Machines to Azure Arc-enabled servers, see [Azure Arc-enabled servers](/azure/azure-arc/servers/overview).
3737

@@ -107,7 +107,7 @@ Assign the `Monitoring Metrics Publisher` role on the workspace's data collectio
107107

108108

109109
### [Microsoft Entra ID application](#tab/entra-application)
110-
### Remote-write using Microsoft Entra ID application authentication.
110+
### Remote-write using Microsoft Entra ID application authentication
111111

112112
To configure remote-write to Azure Monitor workspace using a Microsoft Entra ID application, create an Entra application and assign it the `Monitoring Metrics Publisher` role on the workspace's data collection rule to the application.
113113

@@ -154,21 +154,21 @@ Assign the `Monitoring Metrics Publisher` role on the workspace's data collectio
154154

155155
1. Select **User, group, or service principal**, and then choose **Select members**. Select the application that you created, and then choose **Select**.
156156

157-
:::image type="content" source="../containers/media/prometheus-remote-write-active-directory/select-application.png" alt-text="Screenshot that shows selecting the application." lightbox="../containers/media/prometheus-remote-write-active-directory/select-application.png":::
157+
:::image type="content" source="media/prometheus-remote-write-virtual-machines/select-members-apps.png" alt-text="Screenshot that shows selecting the application." lightbox="media/prometheus-remote-write-virtual-machines/select-members-apps.png":::
158158

159159
1. To complete the role assignment, select **Review + assign**.
160160

161161
### [CLI](#tab/CLI)
162162
## Create user-assigned identities and Microsoft Entra ID apps using CLI
163163

164-
#### Create a user-assigned managed identity
164+
### Create a user-assigned managed identity
165165

166166
Create a user-assigned managed identity for remote-write using the following steps:
167-
- Create a user-assigned managed identity
168-
- Assign the `Monitoring Metrics Publisher` role on the workspace's data collection rule to the managed identity
169-
- Assign the managed identity to a Virtual Machine or Virtual Machine Scale Set.
167+
1. Create a user-assigned managed identity
168+
1. Assign the `Monitoring Metrics Publisher` role on the workspace's data collection rule to the managed identity
169+
1. Assign the managed identity to a Virtual Machine or Virtual Machine Scale Set.
170170

171-
Note the value of the `clientId` of the managed identity that you created. This ID is used in the Prometheus remote write configuration.
171+
Note the value of the `clientId` of the managed identity that you create. This ID is used in the Prometheus remote write configuration.
172172

173173
1. Create a user-assigned managed identity using the following CLI command:
174174

0 commit comments

Comments
 (0)