This alert triggers when the memory utilization of a Google Cloud Run container exceeds the set threshold. High memory usage can lead to resource exhaustion, potentially causing containers to crash or restart. Customization Guidance: Threshold: Set the threshold to trigger if memory utilization exceeds 80% over a 10-minute period. Adjust this based on the memory allocation and resource needs of your containers. Service Specificity: Monitor memory utilization for services that are memory-intensive or critical for application stability. Notification Frequency: Trigger alerts when high memory usage is detected to prevent container crashes or memory exhaustion. Action: Investigate memory usage to identify any memory leaks or processes consuming excessive memory. Consider scaling resources or optimizing memory management within the container.

This alert triggers when the CPU utilization of a Google Cloud Run container exceeds the defined threshold. High CPU usage can lead to performance bottlenecks and slow responses. Customization Guidance: Threshold: Set the threshold to trigger when CPU utilization exceeds 80% over a 10-minute period. Adjust this based on the specific performance needs of your services. Service Specificity: Monitor critical services and revisions that are resource-intensive or require consistent CPU availability. Notification Frequency: Trigger alerts when high CPU utilization is detected to prevent performance degradation. Action: Investigate high CPU usage to determine if additional resources are needed or if optimizations to container processes can be made to reduce load.

This alert triggers when the container startup latency for a Google Cloud Run service exceeds the defined threshold. Slow startup times can lead to delays in service availability, especially in cold-start scenarios. Customization Guidance: Threshold: Set the threshold to trigger if container startup latency exceeds 1000 milliseconds, but adjust according to the acceptable startup time for your services. Service Specificity: Focus on critical services and revisions where fast container startups are necessary for meeting SLAs. Notification Frequency: Trigger alerts upon detecting slow container startup times to avoid service interruptions or delays. Action: Investigate potential reasons for delayed startup, such as container image size, dependencies, or system resource availability. Optimize container startup processes or configurations if necessary.

This alert triggers when the request latency for a Google Cloud Run service exceeds a specified threshold. High request latency can indicate performance issues, potentially leading to slower response times and degraded user experience. Customization Guidance: Threshold: Set the threshold to trigger when the request latency exceeds 500 milliseconds over a 10-minute window, depending on your application’s performance expectations. Service Specificity: Monitor latency on critical services and revisions that are vital to performance or user-facing features. Notification Frequency: Trigger alerts when request latency consistently breaches the threshold to ensure timely action. Action: Investigate the causes of high latency, such as network congestion or overloaded services. Consider optimizing service configurations or scaling resources as needed.