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
Copy file name to clipboardExpand all lines: articles/azure-monitor/containers/prometheus-remote-write-troubleshooting.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ ms.date: 4/18/2024
13
13
14
14
# Troubleshoot remote write
15
15
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).
Copy file name to clipboardExpand all lines: articles/azure-monitor/essentials/prometheus-remote-write-virtual-machines.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This article explains how to configure remote-write to send data from a self-man
20
20
21
21
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.
22
22
23
-
####Azure managed Virtual Machines and Virtual Machine Scale Sets
23
+
## Azure managed Virtual Machines and Virtual Machine Scale Sets
24
24
25
25
Use user-assigned managed identity authentication for services running self managed Prometheus in an Azure environment. Azure managed services include:
26
26
@@ -31,7 +31,7 @@ Use user-assigned managed identity authentication for services running self mana
31
31
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).
32
32
33
33
34
-
####Virtual machines running on non-Azure environments.
34
+
## Virtual machines running on non-Azure environments.
35
35
36
36
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).
37
37
@@ -107,7 +107,7 @@ Assign the `Monitoring Metrics Publisher` role on the workspace's data collectio
107
107
108
108
109
109
### [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
111
111
112
112
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.
113
113
@@ -154,21 +154,21 @@ Assign the `Monitoring Metrics Publisher` role on the workspace's data collectio
154
154
155
155
1. Select **User, group, or service principal**, and then choose **Select members**. Select the application that you created, and then choose **Select**.
156
156
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":::
158
158
159
159
1. To complete the role assignment, select **Review + assign**.
160
160
161
161
### [CLI](#tab/CLI)
162
162
## Create user-assigned identities and Microsoft Entra ID apps using CLI
163
163
164
-
####Create a user-assigned managed identity
164
+
### Create a user-assigned managed identity
165
165
166
166
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.
170
170
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.
172
172
173
173
1. Create a user-assigned managed identity using the following CLI command:
0 commit comments