Skip to content

Commit 62ad507

Browse files
Merge pull request #275069 from sunasing/sunasing-br-0510
Add minor note in Windows metrics collection setup
2 parents 909c518 + 18cacfd commit 62ad507

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -631,8 +631,7 @@ This option enables Prometheus metrics on a cluster without enabling Container i
631631
632632
As of version 6.4.0-main-02-22-2023-3ee44b9e of the Managed Prometheus addon container (prometheus_collector), Windows metric collection has been enabled for the AKS clusters. Onboarding to the Azure Monitor Metrics add-on enables the Windows DaemonSet pods to start running on your node pools. Both Windows Server 2019 and Windows Server 2022 are supported. Follow these steps to enable the pods to collect metrics from your Windows node pools.
633633
634-
1. Manually install windows-exporter on AKS nodes to access Windows metrics.
635-
Enable the following collectors:
634+
1. Manually install windows-exporter on AKS nodes to access Windows metrics by deploying the [windows-exporter-daemonset YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file. Enable the following collectors:
636635
637636
* `[defaults]`
638637
* `container`
@@ -642,7 +641,7 @@ As of version 6.4.0-main-02-22-2023-3ee44b9e of the Managed Prometheus addon con
642641
643642
For more collectors, please see [Prometheus exporter for Windows metrics](https://github.com/prometheus-community/windows_exporter#windows_exporter).
644643
645-
Deploy the [windows-exporter-daemonset YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file:
644+
Deploy the [windows-exporter-daemonset YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file. Note that if there are any taints applied in the node, you will need to apply the appropriate tolerations.
646645
647646
```
648647
kubectl apply -f windows-exporter-daemonset.yaml
@@ -653,8 +652,7 @@ As of version 6.4.0-main-02-22-2023-3ee44b9e of the Managed Prometheus addon con
653652
654653
* If onboarding using the CLI, include the option `--enable-windows-recording-rules`.
655654
* If onboarding using an ARM template, Bicep, or Azure Policy, set `enableWindowsRecordingRules` to `true` in the parameters file.
656-
* If the cluster is already onboarded, use [this ARM template](https://github.com/Azure/prometheus-collector/blob/main/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRules.json) and [this parameter file](https://github.com/Azure/prometheus-collector/blob/main/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRulesParameters.json) to create the rule groups.
657-
655+
* If the cluster is already onboarded, use [this ARM template](https://github.com/Azure/prometheus-collector/blob/main/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRules.json) and [this parameter file](https://github.com/Azure/prometheus-collector/blob/main/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRulesParameters.json) to create the rule groups. This will add the required recording rules and is not an ARM operation on the cluster and does not impact current monitoring state of the cluster.
658656
659657
660658

0 commit comments

Comments
 (0)