This alert has detected high TCP round-trip time (RTT) in HTTPS requests for a URL map in GCP Load Balancing. The alert is activated when the maximum TCP RTT exceeds 100 milliseconds for a continuous period of 10 minutes. Customization Guidance: Threshold: The default threshold is set at 100 milliseconds. Depending on your specific application needs and past performance data, this threshold may need adjustment. Critical services with low latency requirements may need a lower threshold. URL Map Specificity: Tailor alerts for different URL maps based on their roles and criticality in your infrastructure. Critical URL maps handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the applications supported by the URL maps. Action: Upon triggering of this alert, immediate actions include reviewing recent TCP RTT logs, checking for network issues, and ensuring that the network and frontend services are performing optimally. Mitigating issues may involve optimizing the network or frontend services.

This alert has detected high latency in HTTPS requests for a backend in GCP Load Balancing. The alert is activated when the maximum backend latency exceeds 300 milliseconds for a continuous period of 10 minutes. Customization Guidance: Threshold: The default threshold is set at 300 milliseconds. Depending on your specific application needs and past performance data, this threshold may need adjustment. Critical backends with low latency requirements may need a lower threshold. Backend Specificity: Tailor alerts for different backends based on their roles and criticality in your infrastructure. Critical backends handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the applications supported by the backends. Action: Upon triggering of this alert, immediate actions include reviewing recent backend latency logs, checking for backend performance issues, and ensuring that backend services are configured and optimized correctly. Mitigating issues may involve optimizing the backend services or infrastructure.

This alert has detected high total latency in HTTPS requests for a URL map in GCP Load Balancing. The alert is activated when the maximum total latency exceeds 500 milliseconds for a continuous period of 10 minutes. Customization Guidance: Threshold: The default threshold is set at 500 milliseconds. Depending on your specific application needs and past performance data, this threshold may need adjustment. Critical services with low latency requirements may need a lower threshold. URL Map Specificity: Tailor alerts for different URL maps based on their roles and criticality in your infrastructure. Critical URL maps handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the applications supported by the URL maps. Action: Upon triggering of this alert, immediate actions include reviewing recent latency logs, checking for network issues, and ensuring that backend services are performing optimally. Mitigating issues may involve optimizing the network or backend services.