Skip to content

Commit 6e48dab

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #271597 from EdB-MSFT/prometheus-curation
Fix Prometheus TOC
2 parents 02d37af + bfa1917 commit 6e48dab

23 files changed

+535
-310
lines changed

‎.openpublishing.redirection.azure-monitor.json

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6688,7 +6688,18 @@
66886688
"source_path_from_root": "/articles/azure-monitor/agents/resource-manager-data-collection-rules.md",
66896689
"redirect_url": "/azure/azure-monitor/essentials/data-collection-rule-create-edit?tabs=arm#manually-create-a-dcr",
66906690
"redirect_document_id": false
6691+
},
6692+
{
6693+
"source_path_from_root": "/articles/azure-monitor/essentials/remote-write-prometheus.md",
6694+
"redirect_url": "/azure/azure-monitor/essentials/prometheus-remote-write-virtual-machines",
6695+
"redirect_document_id": false
6696+
},
6697+
{
6698+
"source_path_from_root": "/articles/azure-monitor/essentials/prometheus-get-started.md",
6699+
"redirect_url": "/azure/azure-monitor/essentials/prometheus-metrics-overview",
6700+
"redirect_document_id": false
66916701
}
6702+
66926703

66936704
]
66946705
}

‎articles/azure-monitor/containers/prometheus-remote-write-active-directory.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to set up remote write in Azure Monitor managed service f
44
author: EdB-MSFT
55
ms.topic: conceptual
66
ms.custom: devx-track-azurecli
7-
ms.date: 2/28/2024
7+
ms.date: 4/18/2024
88
---
99

1010
# Send Prometheus data to Azure Monitor by using Microsoft Entra authentication
@@ -24,7 +24,16 @@ This article applies to the following cluster configurations:
2424
2525
## Prerequisites
2626

27-
The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
27+
### Supported versions
28+
29+
- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication.
30+
31+
### Azure Monitor workspace
32+
33+
This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](/azure/azure-monitor/essentials/azure-monitor-workspace-manage#create-an-azure-monitor-workspace).
34+
35+
## Permissions
36+
Administrator permissions for the cluster or resource are required to complete the steps in this article.
2837

2938
## Set up an application for Microsoft Entra ID
3039

@@ -167,9 +176,9 @@ This step is required only if you didn't turn on Azure Key Vault Provider for Se
167176
168177
## Verification and troubleshooting
169178
170-
For verification and troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
179+
For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting) and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
171180
172-
## Related content
181+
## Next steps
173182
174183
- [Collect Prometheus metrics from an AKS cluster](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana)
175184
- [Learn more about Azure Monitor managed service for Prometheus](../essentials/prometheus-metrics-overview.md)

‎articles/azure-monitor/containers/prometheus-remote-write-azure-ad-pod-identity.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to set up remote write for Azure Monitor managed service
44
author: EdB-MSFT
55
ms.author: edbaynash
66
ms.topic: conceptual
7-
ms.date: 05/11/2023
7+
ms.date: 4/18/2024
88
ms.reviewer: rapadman
99
---
1010

@@ -17,7 +17,17 @@ This article describes how to set up remote write for Azure Monitor managed serv
1717
1818
## Prerequisites
1919

20-
The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
20+
### Supported versions
21+
22+
Prometheus versions greater than v2.45 are required for managed identity authentication.
23+
24+
### Azure Monitor workspace
25+
26+
This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](/azure/azure-monitor/essentials/azure-monitor-workspace-manage#create-an-azure-monitor-workspace).
27+
28+
## Permissions
29+
30+
Administrator permissions for the cluster or resource are required to complete the steps in this article.
2131

2232
## Set up an application for Microsoft Entra pod-managed identity
2333

@@ -100,9 +110,9 @@ The `aadpodidbinding` label must be added to the Prometheus pod for the pod-mana
100110

101111
## Verification and troubleshooting
102112

103-
For verification and troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
113+
For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting) and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
104114

105-
## Related content
115+
## Next steps
106116

107117
- [Collect Prometheus metrics from an AKS cluster](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana)
108118
- [Learn more about Azure Monitor managed service for Prometheus](../essentials/prometheus-metrics-overview.md)

‎articles/azure-monitor/containers/prometheus-remote-write-azure-workload-identity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: azure-monitor
66
ms.author: edbaynash
77
ms.topic: conceptual
88
ms.custom: devx-track-azurecli
9-
ms.date: 09/10/2023
9+
ms.date: 4/18/2024
1010
ms.reviewer: rapadman
1111
---
1212

@@ -16,7 +16,7 @@ This article describes how to set up [remote write](prometheus-remote-write.md)
1616

1717
## Prerequisites
1818

19-
To send data from a Prometheus server by using remote write with Microsoft Entra Workload ID authentication, you need:
19+
- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication.
2020

2121
- A cluster that has feature flags that are specific to OpenID Connect (OIDC) and an OIDC issuer URL:
2222
- For managed clusters (Azure Kubernetes Service, Amazon Elastic Kubernetes Service, and Google Kubernetes Engine), see [Managed Clusters - Microsoft Entra Workload ID](https://azure.github.io/azure-workload-identity/docs/installation/managed-clusters.html).
@@ -179,9 +179,9 @@ az ad app federated-credential create --id ${APPLICATION_OBJECT_ID} --parameters
179179
180180
## Verification and troubleshooting
181181
182-
For verification and troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
182+
For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting) and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
183183
184-
## Related content
184+
## Next steps
185185
186186
- [Collect Prometheus metrics from an AKS cluster](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana)
187187
- [Learn more about Azure Monitor managed service for Prometheus](../essentials/prometheus-metrics-overview.md)

‎articles/azure-monitor/containers/prometheus-remote-write-managed-identity.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Set up Prometheus remote write by using managed identity authentication
33
description: Learn how to set up remote write in Azure Monitor managed service for Prometheus. Use managed identity authentication to send data from a self-managed Prometheus server running in your Azure Kubernetes Server (AKS) cluster or Azure Arc-enabled Kubernetes cluster.
44
author: EdB-MSFT
55
ms.topic: conceptual
6-
ms.date: 2/28/2024
6+
ms.date: 4/18/2024
77
---
88

99
# Send Prometheus data to Azure Monitor by using managed identity authentication
@@ -22,7 +22,17 @@ This article applies to the following cluster configurations:
2222
2323
## Prerequisites
2424

25-
The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
25+
### Supported versions
26+
27+
Prometheus versions greater than v2.45 are required for managed identity authentication.
28+
29+
### Azure Monitor workspace
30+
31+
This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](/azure/azure-monitor/essentials/azure-monitor-workspace-manage#create-an-azure-monitor-workspace).
32+
33+
## Permissions
34+
35+
Administrator permissions for the cluster or resource are required to complete the steps in this article.
2636

2737
## Set up an application for managed identity
2838

@@ -131,9 +141,9 @@ This step isn't required if you're using an AKS identity. An AKS identity alread
131141
132142
## Verification and troubleshooting
133143
134-
For verification and troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
144+
For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting) and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
135145
136-
## Related content
146+
## Next steps
137147
138148
- [Collect Prometheus metrics from an AKS cluster](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana)
139149
- [Learn more about Azure Monitor managed service for Prometheus](../essentials/prometheus-metrics-overview.md)

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

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: Troubleshooting Remote-write in Azure Monitor Managed Service for Prometheus
3+
description: Describes how to troubleshoot remote-write in Azure Monitor Managed Service for Prometheus
4+
author: EdB-MSFT
5+
ms.service: azure-monitor
6+
ms.subservice: essentials
7+
ms-author: edbaynash
8+
ms.topic: conceptual
9+
ms.date: 4/18/2024
10+
11+
# customer intent: As a user of Azure Monitor Managed Service for Prometheus, I want to troubleshoot remote-write issues so that I can ensure that my data is flowing correctly.
12+
---
13+
14+
# Troubleshoot remote write
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).
17+
18+
## Supported versions
19+
20+
- Prometheus versions greater than v2.45 are required for managed identity authentication.
21+
- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication.
22+
23+
24+
## HTTP 403 error in the Prometheus log
25+
26+
It takes about 30 minutes for the assignment of the role to take effect. During this time, you may see an HTTP 403 error in the Prometheus log. Check that you have configured the managed identity or Microsoft Entra ID application correctly with the `Monitoring Metrics Publisher` role on the workspace's data collection rule. If the configuration is correct, wait 30 minutes for the role assignment to take effect.
27+
28+
29+
## No Kubernetes data is flowing
30+
31+
If remote data isn't flowing, run the following command to find errors in the remote write container.
32+
33+
```azurecli
34+
kubectl --namespace <Namespace> describe pod <Prometheus-Pod-Name>
35+
```
36+
37+
38+
## Container restarts repeatedly
39+
40+
A container regularly restarting is likely due to misconfiguration of the container. Run the following command to view the configuration values set for the container. Verify the configuration values especially `AZURE_CLIENT_ID` and `IDENTITY_TYPE`.
41+
42+
```azureccli
43+
kubectl get pod <Prometheus-Pod-Name> -o json | jq -c '.spec.containers[] | select( .name | contains("<Azure-Monitor-Side-Car-Container-Name>"))'
44+
```
45+
46+
The output from this command has the following format:
47+
48+
```
49+
{"env":[{"name":"INGESTION_URL","value":"https://my-azure-monitor-workspace.eastus2-1.metrics.ingest.monitor.azure.com/dataCollectionRules/dcr-00000000000000000/streams/Microsoft-PrometheusMetrics/api/v1/write?api-version=2021-11-01-preview"},{"name":"LISTENING_PORT","value":"8081"},{"name":"IDENTITY_TYPE","value":"userAssigned"},{"name":"AZURE_CLIENT_ID","value":"00000000-0000-0000-0000-00000000000"}],"image":"mcr.microsoft.com/azuremonitor/prometheus/promdev/prom-remotewrite:prom-remotewrite-20221012.2","imagePullPolicy":"Always","name":"prom-remotewrite","ports":[{"containerPort":8081,"name":"rw-port","protocol":"TCP"}],"resources":{},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","volumeMounts":[{"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount","name":"kube-api-access-vbr9d","readOnly":true}]}
50+
```
51+
52+
53+
## Ingestion quotas and limits
54+
55+
When configuring Prometheus remote write to send data to an Azure Monitor workspace, you typically begin by using the remote write endpoint displayed on the Azure Monitor workspace overview page. This endpoint involves a system-generated Data Collection Rule (DCR) and Data Collection Endpoint (DCE). These resources have ingestion limits. For more information on ingestion limits, see [Azure Monitor service limits](../service-limits.md#prometheus-metrics). When setting up remote write for multiple clusters sending data to the same endpoint, you might reach these limits. Consider creating additional DCRs and DCEs to distribute the ingestion load across multiple endpoints. This approach helps optimize performance and ensures efficient data handling. For more information about creating DCRs and DCEs, see [how to create custom Data collection endpoint(DCE) and custom Data collection rule(DCR) for an existing Azure monitor workspace(AMW) to ingest Prometheus metrics](https://aka.ms/prometheus/remotewrite/dcrartifacts).

0 commit comments

Comments
 (0)