Merge pull request #243326 from bragi92/kaveesh/windows_exporter_issue

fix: add note for setting windows exporter limits as it can cause issues on aks nodes

Author: prmerger-automator[bot]

articles/azure-monitor/essentials/prometheus-metrics-enable.md

@@ -386,6 +386,14 @@ Deploy the template with the parameter file by using any valid method for deploy
 
 ## Enable Windows metrics collection
 
+> [!NOTE]
+> There is no CPU/Memory limit in windows-exporter-daemonset.yaml so it may over-provision the Windows nodes  
+> For more details see [Resource reservation](https://kubernetes.io/docs/concepts/configuration/windows-resource-management/#resource-reservation)
+>   
+> As you deploy workloads, set resource memory and CPU limits on containers. This also subtracts from NodeAllocatable and helps the cluster-wide scheduler in determining which pods to place on which nodes.
+> Scheduling pods without limits may over-provision the Windows nodes and in extreme cases can cause the nodes to become unhealthy.
+
+
 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.
 
 1. Manually install windows-exporter on AKS nodes to access Windows metrics.