Question

A payments API team has an alerting policy in Cloud Monitoring that fires when the 5-minute p95 latency exceeds 800 ms. During a period of intermittent load, the underlying condition crosses the threshold repeatedly for short spikes, generating a storm of open-and-close incident notifications that overwhelm the on-call engineer. The team wants to keep the latency threshold but suppress noise from brief, transient spikes without missing a genuinely sustained latency regression. What should they configure?

Accepted Answer

Increase the condition's 'retest window' (duration) so the metric must stay above 800 ms for a longer sustained period before the condition triggers.

Answer

Lower the latency threshold to 500 ms so the condition triggers earlier and stays consistently in the alerting state.

Answer

Disable the notification channel during business hours and rely on dashboard inspection instead.

Answer

Change the aggregation aligner from p95 to max so brief spikes are captured more accurately.