This alert monitors CPU utilization in Azure Virtual Machines (VMs). It is activated when the CPU usage exceeds 90% for any VM, identified by its name, cloud account ID, or cloud region over a 10-minute timeframe. Customization Guidance: Default Threshold: The alert triggers if the CPU usage in an Azure VM exceeds 90%. Adjustment: Depending on your application's specific requirements and performance needs, you may need to adjust this threshold. Applications with high computational demands may require a lower threshold, while those with more relaxed performance requirements may tolerate a higher threshold. VM Relevance: Customize alerts for different Azure VMs based on their importance and role in your infrastructure. Critical VMs that require optimal performance may need more stringent monitoring. Project Specificity: Tailor alerts per project, especially if you manage multiple projects with varying levels of criticality and performance demands. Alert Frequency: Balance between timely alerts and reducing alert fatigue. Adjust the frequency based on the importance of the Azure VMs and the applications they support. Tiered Notifications: Implement a tiered notification system, where critical breaches trigger immediate alerts, while less critical ones may trigger less frequently. Action: Immediate Steps: Upon triggering, immediate actions include reviewing recent logs for the affected VMs, checking for CPU bottlenecks, and ensuring the VM configuration is optimized. Mitigation: To resolve issues, consider optimizing your application code, adjusting your VM size or configuration, or scaling your compute resources to handle higher loads more effectively.

This alert monitors available memory in Azure Virtual Machines (VMs). It is activated when the available memory drops below 100 MB (approximately 104,858,000 bytes) for any VM, identified by its name, cloud account ID, or cloud region over a 10-minute timeframe. Customization Guidance: Default Threshold: The alert triggers if the available memory in an Azure VM drops below 100 MB (104,858,000 bytes). Adjustment: Depending on your application's specific requirements and memory usage patterns, you may need to adjust this threshold. Applications with high memory demands may require a higher threshold, while those with more relaxed memory requirements may tolerate a lower threshold. VM Relevance: Customize alerts for different Azure VMs based on their importance and role in your infrastructure. Critical VMs that require optimal performance may need more stringent monitoring. Project Specificity: Tailor alerts per project, especially if you manage multiple projects with varying levels of criticality and memory demands. Alert Frequency: Balance between timely alerts and reducing alert fatigue. Adjust the frequency based on the importance of the Azure VMs and the applications they support. Tiered Notifications: Implement a tiered notification system, where critical breaches trigger immediate alerts, while less critical ones may trigger less frequently. Action: Immediate Steps: Upon triggering, immediate actions include reviewing recent logs for the affected VMs, checking for memory bottlenecks, and ensuring the VM configuration is optimized. Mitigation: To resolve issues, consider optimizing your application code to reduce memory usage, adjusting your VM size or configuration, or scaling your memory resources to handle higher loads more effectively.

This alert monitors the remaining CPU credits in Azure Virtual Machines (VMs). It is activated when the CPU credits fall below 10 for any VM, identified by its cloud account ID, cloud region, or VM name over a 15-minute timeframe. Customization Guidance: Default Threshold: The alert triggers if the CPU credits in an Azure VM fall below 10. Adjustment: Depending on your application's specific requirements and CPU usage patterns, you may need to adjust this threshold. Applications with high computational demands may require a higher threshold, while those with more relaxed performance requirements may tolerate a lower threshold. VM Relevance: Customize alerts for different Azure VMs based on their importance and role in your infrastructure. Critical VMs that require optimal performance may need more stringent monitoring. Project Specificity: Tailor alerts per project, especially if you manage multiple projects with varying levels of criticality and CPU demands. Alert Frequency: Balance between timely alerts and reducing alert fatigue. Adjust the frequency based on the importance of the Azure VMs and the applications they support. Tiered Notifications: Implement a tiered notification system, where critical breaches trigger immediate alerts, while less critical ones may trigger less frequently. Action: Immediate Steps: Upon triggering, immediate actions include reviewing recent logs for the affected VMs, checking for CPU usage patterns, and ensuring the VM configuration is optimized. Mitigation: To resolve issues, consider optimizing your application code to reduce CPU usage, adjusting your VM size or configuration, or managing your workload distribution to ensure efficient use of CPU credits.