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/essentials/prometheus-remote-write-managed-identity.md
+39-44Lines changed: 39 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This article applies to the following cluster configurations:
24
24
## Prerequisites
25
25
26
26
- You must have self-managed Prometheus running on your AKS cluster. For example, see [Using Azure Kubernetes Service with Grafana and Prometheus](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/using-azure-kubernetes-service-with-grafana-and-prometheus/ba-p/3020459).
27
-
- You used Kube-Prometheus Stack when you setup Prometheus on your AKS cluster.
27
+
- You used [Kube-Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) when you setup Prometheus on your AKS cluster.
28
28
29
29
30
30
## Create Azure Monitor workspace
@@ -107,51 +107,46 @@ This step isn't required if you're using an AKS identity since it will already h
107
107
This YAML assumes you're using 8081 as your listening port. Modify that value if you use a different port.
0 commit comments