Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,375 questions
AKS cluster monitoring using Prometheus Alert rules
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 39%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
Chakraborty, Shubham
60
Reputation points
We have received the Microsoft service health advisory regarding monitoring of AKS clusters using custom alerts rules were going to expire on 31st May 2024 and we have to migrate the monitoring using Prometheus alert rules. However, we have configured the monitoring using the Prometheus alert rules now of most of the AKS clusters.
But we are having queries regarding the below:
- All of the custom alert rules based alert are still coming in Azure portal regarding the respective AKS cluster after 31st May 2024. Will they get auto removed or the service health advisory is only applicable on new alert creation and not on existing AKS clusters with custom alert rules enabled?
- We have enabled Prometheus alert rules but when checking the Prometheus alert rule group there are many recording rules also coming in enabled state which we haven't enabled from our end. Can we know the purpose of recording rules, and do we need to keep them in enabled state, and will they incur additional cost?
- In some of the AKS cluster we are not able to configure Prometheus for monitoring and getting error that the cluster is service principal enabled. How can we configure Prometheus in this scenario on the AKS clusters?
Sign in to answer