Other Articles
- SQL Database – Enable Database Encryption
- SQL Databases – Enable Backup
- SQL Database – Monitor CPU Utilization
- SQL Database – Monitor IO Utilization
- SQL Database – Monitor Memory Utilization
- SQL Database – Protect From Direct Internet Traffic
- SQL Server – Enable SQL Defender
- SQL Server – Require Microsoft Entra-Only Authentication
- SQL Server – Block Public Firewall Rules
- SQL Server – Enable Auditing
- Storage Account – Enable Storage Encryption
- Storage Account – Disable Blob Public Access
- Storage Account – Disable Cross-Tenant Replication
- Storage Account – Disable Public Network Access
- Storage Account – Enable Microsoft Defender
- Storage Account – Enable Secure Transfer
- Storage Account – Enforce Minimum TLS Version
- Storage Account – Enforce Network Access Rule
- Storage Account – Enforce Private Endpoint Access
- Storage Account – Enable Blob Soft Delete
- Storage Account – Enable Blob Versioning
- User – Enable Azure MFA
- App Service – Disable Remote Debugging
- App Service – Enable Defender
- App Service – Enable Entra ID Registration
- App Service – Enable HTTP2
- App Service – Enforce Latest TLS Version
- App Service – Enforce Secure FTPS State
- App Service – Monitor Server Errors
- App Service – Redirect HTTP to HTTPS
- Cosmos DB – Enable Backup
- Cosmos DB – Enable Microsoft Defender
- Cosmos DB – Monitor Latency
- Cosmos DB – Ensure Private Connectivity
- Cosmos DB for PostgreSQL – Monitor IO Utilization
- Cosmos DB for PostgreSQL – Monitor Memory Utilization
- Cosmos DB for PostgreSQL – Protect From Direct Internet Traffic
- Cosmos DB – Protect From Direct Internet Traffic
- Cosmos DB – Restrict Firewall Network Access
- Virtual Machine – Enable Defender
- Virtual Machine – Protect From Direct Internet Traffic
- Key Vault – Enable Defender
- Key Vault – Ensure Vault Recoverable
- Key Vault – Require Private Endpoint Access
- Key Vault – Enforce Keys Expiration
- Key Vault – Enable Purge Protection
- Key Vault – Use Azure RBAC Authorization
- MySQL Flexible Server – Enable Audit Log Events Connection
- MySQL Flexible Server – Enable Audit Logs
- MySQL Flexible Server – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Configure Log File Retention
- PostgreSQL Flexible Server – Enable Connection Logging
- PostgreSQL Flexible Server – Enable Connection Throttling
- PostgreSQL Flexible Server – Enable Disconnection Logging
- PostgreSQL Flexible Server – Enable Log Checkpoints
- Network Security Group – Ensure Flow Logs Captured
- General – Enable Auto Provisioning Log Analytics
- General – Enable Security Notifications
- General – Set Additional Email Address
- Cosmos DB – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Enforce Minimum TLS Version
- Container Instance – Enforce Use of Private Virtual Networks
- Container Instance – Enforce Managed Identity Usage
Cosmos DB for PostgreSQL – Monitor CPU Utilization
Secure Configuration Checks > Azure
This check ensures that CPU utilization is actively monitored for Azure Cosmos DB for PostgreSQL (Server Groups v2). Continuous monitoring helps maintain optimal database performance, supports capacity planning, and enables early detection of performance anomalies.
Check Details
- Resource: Azure Cosmos DB for PostgreSQL
- Check: Ensure CPU utilization Is Monitored
- Risk: Without proper CPU monitoring, performance degradation, unexpected workload spikes, or resource exhaustion may go unnoticed, potentially leading to service disruption and reduced application availability.
Remediation via Azure Portal
-
Log in to the Azure Portal.
-
Navigate to Azure Cosmos DB for PostgreSQL and select the relevant server group.
-
Under Monitoring, select Metrics.
-
From the metric drop-down menu, select CPU percent.
-
Configure an Alert rule based on CPU utilization:
- Click New alert rule.
- Define an appropriate threshold (for example, greater than 80%).
- Select an action group for notifications.
- Review and create the alert rule to enable proactive monitoring.
Remediation via Azure CLI
-
Open Azure Cloud Shell or a local terminal with Azure CLI installed.
-
Retrieve available CPU metrics for the server group:
az monitor metrics list-definitions \ --resource <resource-id> \ --query "[?contains(name.value, 'cpu')]"
-
Create a CPU utilization alert rule:
az monitor metrics alert create \ --name "HighCPUAlert" \ --resource-group <resource-group> \ --scopes <resource-id> \ --condition "avg cpu_percent > 80" \ --description "Alert when CPU utilization exceeds 80 percent" \ --evaluation-frequency 5m \ --window-size 5m
-
Verify that the alert rule has been created:
az monitor metrics alert list \ --resource-group <resource-group> \ --output table
Replace
<resource-group>and<resource-id>with your actual values. The alert rule ensures CPU utilization is continuously monitored and appropriate action can be taken when thresholds are exceeded.
Updated on 18 February, 2026