Question

A payments team runs a critical API on GKE. They receive frequent false-positive pages: alerts fire whenever CPU briefly spikes, even though the service remains healthy and responsive. The team wants to only be paged when the service is genuinely degraded — specifically, when high request latency AND an elevated error rate occur together over a sustained window. What is the most appropriate way to configure this in Cloud Monitoring?

Accepted Answer

Create a single alerting policy with multiple conditions joined by a logical AND, using a rolling window (e.g., 5 minutes) on the latency and error-rate metrics so the policy triggers only when both conditions are simultaneously met.

Answer

Create two separate alerting policies — one for latency and one for error rate — each with its own notification channel, so both pages arrive together.

Answer

Create a single alerting policy with the latency and error-rate conditions joined by a logical OR so any signal of trouble triggers a page.

Answer

Lower the CPU alerting threshold and add a longer duration window so transient CPU spikes are filtered out before paging.