This alert monitors CPU utilization by priority in Google Cloud Spanner instances. It is activated when the CPU utilization exceeds 80% for any priority level. Customization Guidance: Default Threshold: The alert triggers if the CPU utilization by priority in a Spanner instance exceeds 80%. Adjustment: Depending on your application's specific requirements and resource demands, you may need to adjust this threshold. Applications with high-performance needs may require a lower threshold, while those with more relaxed requirements may tolerate a higher threshold. Instance Relevance: Customize alerts for different Spanner instances based on their importance and role in your infrastructure. Critical instances 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 resource demands. Alert Frequency: Balance between timely alerts and reducing alert fatigue. Adjust the frequency based on the importance of the Spanner instances 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 instances, checking for performance bottlenecks, and ensuring the Spanner configuration is optimized. Mitigation: To resolve issues, consider optimizing your queries, adjusting your Spanner instance configuration, or scaling your resources to handle higher loads more effectively.

This alert monitors storage utilization in Google Cloud Spanner instances. It is activated when the storage utilization exceeds 90% for any database, instance, location, or API domain. Customization Guidance: Default Threshold: The alert triggers if the storage utilization in a Spanner instance exceeds 90%. Adjustment: Depending on your application's specific requirements and storage needs, you may need to adjust this threshold. Applications with high storage demands may require a lower threshold, while those with more relaxed requirements may tolerate a higher threshold. Instance Relevance: Customize alerts for different Spanner instances based on their importance and role in your infrastructure. Critical instances 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 storage demands. Alert Frequency: Balance between timely alerts and reducing alert fatigue. Adjust the frequency based on the importance of the Spanner instances 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 instances, checking for storage bottlenecks, and ensuring the Spanner configuration is optimized. Mitigation: To resolve issues, consider optimizing your data schema, adjusting your Spanner instance configuration, or scaling your storage resources to handle higher loads more effectively.