AKS Cluster Monitoring Not Enabled
Cluster and node metrics are not collected, so resource exhaustion is only visible once workloads start failing.
Free to start. No card. The playground just needs your work email.
AzureKubernetes
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable monitoring on the AKS cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- AKS Clusters on Azure
- The fix, by hand
- AKS → the resource → Monitoring → Insights.
- Click Configure → pick (or create) a Log Analytics workspace in the same region.
- Enable Container Insights; AKS deploys the ama-logs DaemonSet automatically.
- Under Monitoring → Workbooks, pin the Cluster, Nodes, and Controllers workbooks for daily review.
- Open Monitor → Alerts → enable the AKS recommended alerts pack (node not ready, pod restarts, disk pressure).
- Confirm metrics arrive: Insights → Cluster view should show CPU/memory within 15 minutes.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1352- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.