This alert identifies a Cloud SQL database with critically low available disk space. It triggers when the remaining disk space for any database falls below a predefined threshold (typically set to 3 GB or another value you define). The alert monitors the difference between the total disk quota and the used disk space for each database. Customization Guidance: Threshold: The default threshold is set at 3 GB. You can adjust this based on your specific database storage needs and acceptable usage levels. Applications with significant data requirements might necessitate a higher threshold to prevent disruptions. Database Specificity: While this alert monitors available disk space for each database, you can investigate further to identify the specific database(s) approaching capacity limits. Notification Frequency: Balance responsiveness with alert fatigue by setting an appropriate notification frequency. Consider the criticality of the data and services dependent on the database when determining the frequency. For example, more critical applications may require more frequent checks. Action: When triggered, this alert prompts immediate action to manage disk space. This may involve: Cleaning up unnecessary or temporary files. Archiving or transferring data to another storage location. Increasing the disk quota for the affected database. Reviewing and optimizing data usage patterns to prevent future capacity issues.

This alert identifies Cloud SQL databases experiencing high CPU utilization. It triggers when the maximum CPU usage for any database exceeds 80%. The alert monitors the peak CPU utilization to ensure that your databases are performing optimally and are not experiencing performance bottlenecks due to excessive CPU load. Customization Guidance: Threshold: The default threshold is set at 80%. You can adjust this based on the performance requirements and acceptable CPU usage levels for your databases. If your applications have high computational needs, consider fine-tuning the threshold to balance performance with resource usage. Database Specificity: This alert monitors maximum CPU utilization for each database. Upon triggering, further investigation can identify specific databases or queries contributing to high CPU load. This helps in pinpointing and addressing the source of performance issues. Notification Frequency: Balance the need for timely responses with the risk of alert fatigue by setting an appropriate notification frequency. Consider the criticality of the database operations and the impact of high CPU usage when determining how often to receive notifications. More critical applications might require more frequent checks. Action: When triggered, this alert prompts immediate action to manage CPU load and optimize database performance. Recommended actions include: Analyzing and optimizing SQL queries to reduce CPU consumption. Scaling up the instance to allocate more CPU resources. Distributing the workload across multiple databases or instances to balance CPU usage. Investigating and mitigating any long-running or CPU-intensive processes contributing to the high usage.

This alert monitors Google Cloud SQL databases to identify instances where disk space utilization falls below 10%. It triggers when the maximum disk utilization ratio for any database exceeds the threshold, ensuring proactive management of storage capacity to prevent operational disruptions. Customization Guidance: Threshold: The default threshold is set at 10%. Adjust this threshold based on your database storage requirements and acceptable disk utilization levels. Consider the growth rate of your database and storage limits to fine-tune alerts for optimal resource management. Database Specificity: This alert monitors maximum disk utilization for each database instance. Upon triggering, investigate specific databases and their storage usage patterns to identify potential capacity issues or inefficient data management practices. Notification Frequency: Balance timely notifications with avoiding alert fatigue by setting an appropriate frequency. Consider the criticality of your database operations and the impact of low disk space on performance when determining notification intervals. Action: When triggered, take immediate action to manage disk space efficiently and maintain database performance: Monitor and optimize database storage usage, including archiving or deleting unnecessary data. Resize the storage capacity of the Cloud SQL instance to accommodate increasing data volumes. Implement automated alerts or procedures to proactively manage storage capacity and prevent future incidents of low disk space.